From: Keith Owens <kaos@melbourne.sgi.com>
To: linux-mips@oss.sgi.com, linux-mips@fnet.fr
Subject: Re: Kernel compiler
Date: Sat, 04 Nov 2000 14:13:37 +1100 [thread overview]
Message-ID: <5652.973307617@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 04 Nov 2000 03:53:26 BST." <20001104035326.A29005@bacchus.dhis.org>
On Sat, 4 Nov 2000 03:53:26 +0100,
Ralf Baechle <ralf@oss.sgi.com> wrote:
>The reports regarding egcs 2.96 and newer misscompiling the kernel only
>affect x86 or are other architecture affected as well? I don't have any
>pending compiler >= 2.96 related bug reports.
At a guess (and it is only a guess), the problems will affect all
architectures. AFAICT they are in the common optimization phase, the
kernel uses constructs that were undefined or poorly defined but worked
in gcc 2.95, 2.96 handles them differently.
next prev parent reply other threads:[~2000-11-04 3:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 21:19 Kernel compiler Ralf Baechle
2000-11-04 2:44 ` Keith Owens
2000-11-04 2:53 ` Ralf Baechle
2000-11-04 3:03 ` Keith M Wesolowski
2000-11-04 3:10 ` Pete Popov
2000-11-04 3:20 ` Ralf Baechle
2000-11-04 3:13 ` Keith Owens [this message]
2000-11-04 10:40 ` Alan Cox
2000-11-04 10:40 ` Alan Cox
2000-11-07 3:39 ` 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=5652.973307617@ocs3.ocs-net \
--to=kaos@melbourne.sgi.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
/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