mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Axel Reinhold <axel@freakout.de>
To: linux-kernel@vger.kernel.org
Subject: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
Date: Sun, 5 Aug 2007 10:56:04 +0200 (CEST)	[thread overview]
Message-ID: <200708050856.l758u4ou031651@bongo.freakout.de> (raw)

i found a bug in linux-2.4.35.

the bug produces a crashing kernel when compiled
with gcc >=4.2.0 and VIA C3 optimized -march=c3
(CONFIG_MCYRIXIII=y)

this issue was first discussed on the gcc bugzilla:
 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32264

and tracked down to the include/asm-i386/hw_irq.h
module with the help of the gcc guys:

(pluto at agmk dot net) wrote:
>yup, i see something new :)
>
>please look at line 12137 of i8259.i:
>
>__attribute__((regparm(0))) void call_do_IRQ(void); __asm__(...
>
>as you can see there is a semicolon after call_do_IRQ(void)
>and following asm statement isn't treated as a function body.
>in this way -O1 -f{no-}unit-at-a-time accidentally produces
>different code. it's not a gcc bug.
>
>linux-2.4.35/include/asm-i386/hw_irq.h
>contains these evil macros.

is there a chance to fix this?
these macros a far beyond my capabilities to fix.

Axel

             reply	other threads:[~2007-08-05  8:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05  8:56 Axel Reinhold [this message]
2007-08-05  9:49 ` Willy Tarreau
2007-08-05 15:43 ` Willy Tarreau
2007-08-05 19:17   ` Willy Tarreau
2007-08-06 13:05   ` Segher Boessenkool
2007-08-06 13:26     ` Willy Tarreau
2007-08-06 17:39       ` H. Peter Anvin
2007-08-06 17:45         ` Willy Tarreau
2007-08-06 18:01           ` H. Peter Anvin
2007-08-06 19:13             ` Willy Tarreau
2007-08-06 21:15             ` Segher Boessenkool
2007-08-06 21:16               ` Willy Tarreau
2007-08-07  5:04                 ` Axel Reinhold
2007-08-07  8:12                   ` Willy Tarreau

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=200708050856.l758u4ou031651@bongo.freakout.de \
    --to=axel@freakout.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

all inboxes | Powered by JetHome®