From: Chris Wedgwood <cw@f00f.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Richard Henderson <rth@twiddle.net>,
rusty@rustcorp.com.au, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eliminate warnings in generated module files
Date: Wed, 19 Feb 2003 15:41:42 -0800 [thread overview]
Message-ID: <20030219234142.GB22254@f00f.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302182115500.1923-100000@home.transmeta.com>
On Tue, Feb 18, 2003 at 09:16:35PM -0800, Linus Torvalds wrote:
> Some people are still using 2.95, I think anything past that is long
> since unsupported and not worth worrying about.
I've recently started using 3.2 for testing and it seems, thus far, so
worse than 2.95.x and appears to have fewer bugs in some regards
(i.e. don't seem to go bonkers with register pressure form long long).
At some point, 2.95.x might be considered too old and gcc 3.2+ with
have to be the minimum --- is this time near?
What about MIPS and Sparc64 --- are they still using ancient
compilers?
--cw
next prev parent reply other threads:[~2003-02-19 23:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 2:43 [PATCH] eliminate warnings in generated module files Richard Henderson
2003-02-19 3:29 ` Linus Torvalds
2003-02-19 3:43 ` Richard Henderson
2003-02-19 5:16 ` Linus Torvalds
2003-02-19 6:16 ` Richard Henderson
2003-02-19 20:11 ` Kai Germaschewski
2003-02-19 21:05 ` Richard Henderson
2003-02-20 0:01 ` Rusty Russell
2003-02-19 23:41 ` Chris Wedgwood [this message]
2003-02-25 4:32 ` Rusty Russell
2003-02-25 7:58 ` Richard Henderson
2003-02-25 11:39 ` Rusty Russell
2003-02-25 23:47 ` Linus Torvalds
2003-02-26 1:22 ` Rusty Russell
2003-02-26 1:36 ` Kai Germaschewski
2003-02-26 4:13 ` Rusty Russell
2003-02-26 17:02 ` Horst von Brand
2003-02-26 17:04 ` Richard Henderson
2003-02-26 3:35 ` Randy.Dunlap
2003-02-26 4:08 ` Rusty Russell
2003-02-26 13:45 ` Werner Almesberger
2003-02-25 21:42 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 2:23 Milton D. Miller II
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=20030219234142.GB22254@f00f.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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