From: "Stuart Yoder" <stuart.yoder@conformative.com>
To: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>
Subject: version of gcc
Date: Thu, 11 Mar 2004 14:12:25 -0600 [thread overview]
Message-ID: <03e401c407a5$2bd19410$3000a8c0@foundation> (raw)
The 2.4 kernel Documentation/Changes file has the following note:
The recommended compiler for the kernel is gcc 2.95.x (x >= 3), and it
should be used when you need absolute stability. You may use gcc 3.0.x
instead if you wish, although it may cause problems. Later versions of gcc
have not received much testing for Linux kernel compilation, and there are
almost certainly bugs (mainly, but not exclusively, in the kernel) that
will need to be fixed in order to use these compilers.
Is this still true? The comment appears to be > 2 years old. I am running
gcc 3.2.2 and wondering if I'm asking for trouble. Do I really need to
revert back to an old compiler?
Thanks,
Stuart
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-03-11 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 20:12 Stuart Yoder [this message]
2004-03-11 20:51 ` version of gcc Mark Hatle
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='03e401c407a5$2bd19410$3000a8c0@foundation' \
--to=stuart.yoder@conformative.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).