From: Andi Kleen <andi@firstfloor.org>
To: "Brian O'Mahoney" <omb@bluewin.ch>
Cc: gcc@gcc.gnu.org, opensuse@opensuse.org, gcc-help@gcc.gnu.org
Subject: Re: gcc and the kernel
Date: Tue, 30 Dec 2008 09:57:00 -0000 [thread overview]
Message-ID: <87ocyuukoq.fsf@basil.nowhere.org> (raw)
In-Reply-To: <200812291522.31842.omb@bluewin.ch> (Brian O'Mahoney's message of "Mon, 29 Dec 2008 15:22:31 -0500")
"Brian O'Mahoney" <omb@bluewin.ch> writes:
>
> Last, a word to the wise, compiler developers, are by nature fairly agressive
> but, unless you want to work on gcc itself, it is wise to stay a bit behind
> the bleeding edge, and, unless your systems are excellently backed up,
> ___DONT_BUILD_THE_KERNEL___ with and untested gcc. I mean a kernel you are
> going to try to run. For an example of why not see the 'ix68 string
> direction' fiasco noting that an interrupt can happen anywhere and that the
> CPU x flag is a non-deterministic (to the interrupt code) part of the
> interrupted context. Oh what fun!
This particular problem has nothing to do with the compiler that built the
kernel.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-12-30 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 20:38 Brian O'Mahoney
2008-12-30 1:54 ` Steven Bosscher
2008-12-30 9:57 ` Andi Kleen [this message]
2008-12-30 10:01 ` Andrew Haley
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=87ocyuukoq.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=omb@bluewin.ch \
--cc=opensuse@opensuse.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).