From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: recommended gcc compiler version
Date: 22 Dec 2000 11:17:58 -0800 [thread overview]
Message-ID: <9209d6$7nt$1@penguin.transmeta.com> (raw)
In-Reply-To: <0012212320430F.02217@comptechnews> <001901c06bdf$1d6c74e0$3b42b0d1@pittscomp.com> <20001221230819.A1678@scutter.internal.splhi.com>
In article <20001221230819.A1678@scutter.internal.splhi.com>,
Tim Wright <timw@splhi.com> wrote:
>
>So....
>egcs-1.1.2 is good for either, 2.7.2 is OK for 2.2, bad for 2.4. 2.95.2 and
>later are risky. RedHat just released a bugfixed "2.96" which is an unknown
>quantity AFAIK. Anybody brave enough to try it should probably post their
>results.
Note that despite my public comments about it beign a bad idea to ship
extremely untested compilers in a major release, I actually think that
it would be wonderful to have people who are ready to face the
consequences to try the new 2.96.
It's not been all that widely tested, but if you kno a bit about what
you're doing (or want to learn), gcc-2.96 _does_ potentially create
better code, and if nobody is willing to test it, any potential bugs (be
they in the kernel sources and triggered by a smarter compiler, or in
the compiler itself) won't be found.
So please do try it out, but please mention the fact if you end up
having to report a bug (it won't make your bug-report be ignored, don't
ever worry about something like that. But i would be good to have an
older compiler handy to correlate the bug with the compiler for sure).
In fact, I'd love to hear about experiences even with the CVS snapshots.
I just don't like them showing up in distributions ;)
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-22 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 4:20 recommended gcc compiler version Robert B. Easter
2000-12-22 6:19 ` Matthew D. Pitts
2000-12-22 7:08 ` Tim Wright
2000-12-22 19:17 ` Linus Torvalds [this message]
2000-12-23 15:55 ` Matthew Vanecek
2000-12-22 7:00 ` Barry K. Nathan
2000-12-22 18:09 ` Andreas Dilger
2000-12-22 8:51 ` Alan Cox
2000-12-22 10:54 ` Rogier Wolff
2000-12-22 11:53 ` Anuradha Ratnaweera
2000-12-24 9:14 ` Kai Henningsen
2000-12-26 8:06 ` Anuradha Ratnaweera
2000-12-22 19:25 ` Linus Torvalds
2000-12-22 20:11 ` Andi Kleen
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='9209d6$7nt$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.