public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Errors in aa2
Date: Sat, 18 Nov 2000 19:37:28 +0100	[thread overview]
Message-ID: <20001118193728.A4607@werewolf.able.es> (raw)
In-Reply-To: <20001118033609.C4381@werewolf.able.es> <20001118181937.I2512@athlon.random>
In-Reply-To: <20001118181937.I2512@athlon.random>; from andrea@suse.de on Sat, Nov 18, 2000 at 18:19:37 +0100


On Sat, 18 Nov 2000 18:19:37 Andrea Arcangeli wrote:
> On Sat, Nov 18, 2000 at 03:36:09AM +0100, J . A . Magallon wrote:
> > /usr/bin/kgcc -D__KERNEL__ -I/usr/src/linux/include -Wall
> -Wstrict-prototypes
> > -O4 -fomit-frame-pointer -fno-strict-aliasing -D__SMP__ -pipe
> > -fno-strength-reduce -march=i686 -malign-loops=2 -malign-jumps=2
> > -malign-functions=2 -DCPU=686   -c -o time.o time.c
> > time.c: In function `do_gettimeofday':
> > time.c:727: fixed or forbidden register 0 (ax) was spilled for class AREG.
> > This may be due to a compiler bug or to impossible asm
> > statements or clauses.
> 
> That's compiler bug obviously.
> 
> Anyways I guess you're triggering compiler bugs because of the weird
> optimizations (-O4). Note also that everything over -O2 is _wrongly_ used to
> inline everything and that will trash away all your icache (I remeber
> also Linus complained about that bad behaviour of >-O2 in the past and
> it's also trivial to fix [shouldn't be more than a one liner], but nobody on
> the gcc side seems to care to fix it since it's still impling the
> inline-functions in gcc CVS of a few weeks ago).
> 

Thanks. I tried to do "by hand" the inlining (just cut and paste, the proc
seemed
not to be used anywhere but time.c), but the result was the same. So looked at
the
gcc info and saw that the function was being inlined from opt level 3.
Also realized that the 'O4' level does not exist in gcc ( I think i 'ported' it
from
use of IRIX cc), so just O2 is right.

Anyway, you can compile somehing with -O9751, and gcc says nothing. If max opt
level
is 3, any higher level should trig a warning at least...

-- 
Juan Antonio Magallon Lacarta                                 #> cd /pub
mailto:jamagallon@able.es                                     #> more beer

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-18 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18  2:36 Errors in aa2 J . A . Magallon
2000-11-18 17:19 ` Andrea Arcangeli
2000-11-18 18:37   ` J . A . Magallon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20001118193728.A4607@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox