linux-mips
[Top] [All Lists]

Re: gcc -3.4.4 and linux-2.4.32

To: David Daney <ddaney@avtrex.com>
Subject: Re: gcc -3.4.4 and linux-2.4.32
From: "P. Christeas" <p_christ@hol.gr>
Date: Thu, 19 Jan 2006 00:35:17 +0200
Cc: Kishore K <hellokishore@gmail.com>, linux-mips@linux-mips.org
In-reply-to: <200601171426.10317.p_christ@hol.gr>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <f07e6e0601160423h5ce1c0d7lcb7e38f8509c4116@mail.gmail.com> <43CBD91B.4020607@avtrex.com> <200601171426.10317.p_christ@hol.gr>
Sender: linux-mips-bounce@linux-mips.org
User-agent: KMail/1.9
On Tuesday 17 January 2006 2:26 pm, P. Christeas wrote:

>
> Does that apply to gcc-4.0.2 as well? It is mentioned in linux
> documentation that -funit-at-a-time is safe as of gcc-4.x. Is there (I'm
> not a MIPS expert) a way to verify whether gcc produces wrong instructions?
> I've had a similar problem (I only try with gcc 4, because I compile linux
> 2.6) and is reduced when I use -fno-unit-at-a-time. Still, I have
> instability, which now appears less often.
> I've tried the '-fno-unit-at-a-time' solution (for the whole kernel) and
> the 'pop/push' at interrupt.h fix.
>
Just to let you know:
In a very interesting twist, gcc4.0.2 produces a faulty kernel with the 2.4.31 
kernel (as the latter is provided from the hardware's manufacturer).
I'm validating gcc and binutils at the moment.

<Prev in Thread] Current Thread [Next in Thread>