[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070805094916.GE6002@1wt.eu>
Date: Sun, 5 Aug 2007 11:49:16 +0200
From: Willy Tarreau <w@....eu>
To: Axel Reinhold <axel@...akout.de>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
On Sun, Aug 05, 2007 at 10:56:04AM +0200, Axel Reinhold wrote:
> 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.
That's one of the ugliest things I've discovered to date !
I have no idea how to fix it, I'm downloading gcc-4.2 right now to try
to find a solution. I've never compiled 2.4 with gcc 4.2, so there may
be surprises.
Regards,
Willy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists