Re: raising severity of reports filed for packages build-depending on gcc-3.2
On Sun, May 09, 2004 at 06:43:06PM +0100, Martin Michlmayr wrote:
> > The only trouble report that might be related is palo (boot loader,
> > aka iplboot) built with gcc-3.3.x does NOT work and same source code
> > built with gcc 3.0.x does. We haven't narrowed this down yet as debugging
> > the boot loader env is, uhm, somewhat unfriendly.
> This is strange because it seems palo in Debian is being compiled with
> 3.3 (or the maintainer uses 3.0 locally and hasn't used a propery
Yes. And the current v1.4 palo in the pool does NOT boot on my c3600
and is reproducible by a few others with other machines.
When I downgrade to palo v1.3 in the pool it works fine.
I build palo 1.3 with gcc 3.3.3 and it doesn't work.
I've talked to Paul Bame (palo maintainer) and he calls this his
"hesienbug". Add some printk's and the bug stops being reproducible.
It's been around for quit a while and we have no proof it's a problem
specifically with gcc 3.3.x. It's non-trivial to debug since iplboot
runs in "real mode" and there is no debug environment.