From: "P. Christeas" <p_christ@hol.gr>
To: David Daney <ddaney@avtrex.com>
Cc: Kishore K <hellokishore@gmail.com>, linux-mips@linux-mips.org
Subject: Re: gcc -3.4.4 and linux-2.4.32
Date: Thu, 19 Jan 2006 00:35:17 +0200 [thread overview]
Message-ID: <200601190035.19022.p_christ@hol.gr> (raw)
In-Reply-To: <200601171426.10317.p_christ@hol.gr>
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.
next prev parent reply other threads:[~2006-01-18 22:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 12:23 gcc -3.4.4 and linux-2.4.32 Kishore K
2006-01-16 12:23 ` Kishore K
2006-01-16 17:34 ` David Daney
2006-01-17 12:07 ` Kishore K
2006-01-17 12:26 ` P. Christeas
2006-01-18 22:35 ` P. Christeas [this message]
2006-01-19 10:00 ` Geert Uytterhoeven
2006-01-19 10:30 ` P. Christeas
2006-01-19 12:33 ` "useless" pgprot_noncached define in include/asm-mips/pgtable.h Niels Sterrenburg
2006-01-23 15:54 ` Atsushi Nemoto
2006-01-17 13:43 ` gcc -3.4.4 and linux-2.4.32 Ralf Baechle
2006-01-17 13:40 ` Ralf Baechle
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=200601190035.19022.p_christ@hol.gr \
--to=p_christ@hol.gr \
--cc=ddaney@avtrex.com \
--cc=hellokishore@gmail.com \
--cc=linux-mips@linux-mips.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