linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>,
	Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: cw@f00f.org, torvalds@transmeta.com, geert@linux-m68k.org,
	alan@lxorguk.ukuu.org.uk, perex@suse.cz,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Isapnp warning
Date: Sat, 21 Jun 2003 20:43:52 -0700	[thread overview]
Message-ID: <90770000.1056253431@[10.10.2.4]> (raw)
In-Reply-To: <20030621191705.3c1dbb16.akpm@digeo.com>

--Andrew Morton <akpm@digeo.com> wrote (on Saturday, June 21, 2003 19:17:05 -0700):

> Arnaldo Carvalho de Melo <acme@conectiva.com.br> wrote:
>> 
>> Em Sat, Jun 21, 2003 at 08:41:02PM -0500, Chris Wedgwood escreveu:
>> > On Sat, Jun 21, 2003 at 09:11:01PM -0300, Arnaldo Carvalho de Melo wrote:
>> > 
>> > > Humm, I'd love to do that, i.e. to make gcc 3 required, lots of good
>> > > stuff like this one, anonymous structs, etc, etc, lots of stuff
>> > > could be done in an easier way, but are we ready to abandon gcc
>> > > 2.95.*? Can anyone confirm if gcc 2.96 accepts this?
>> > 
>> > What *requires* 2.96 still?  Is it a large number of people or obscure
>> > architecture?
>> 
>> I don't know, I was just trying to figure out the impact of requiring gcc 3
>> to compile the kernel. I never used gcc 2.96 btw.
>> 
> 
> Compared to 2.95.3, gcc-3.3 takes 1.5x as long to compile, and produces a
> kernel which is 200k larger.
> 
> It is simply worthless.

Agreed. 2.95.4 is also still the default debian compiler. Requiring
3.x seems like a bad plan, until they get it to a point where it's
actually better than 2.95, stable, and widely distributed. It's 
definitely not there yet (seems kind of stable, but not the others).

M.


  parent reply	other threads:[~2003-06-22  3:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15 18:36 [PATCH] Isapnp warning Geert Uytterhoeven
2003-06-21 12:31 ` Alan Cox
2003-06-21 14:59   ` Geert Uytterhoeven
2003-06-21 15:04     ` Sean Neakums
2003-06-21 19:51     ` Andrew Morton
2003-06-21 23:53       ` Linus Torvalds
2003-06-22  0:11         ` Arnaldo Carvalho de Melo
2003-06-22  1:41           ` Chris Wedgwood
2003-06-22  1:43             ` Arnaldo Carvalho de Melo
2003-06-22  2:17               ` Andrew Morton
2003-06-22  2:27                 ` Chris Wedgwood
2003-06-22  2:59                   ` Andrew Morton
2003-06-22  5:50                     ` Herbert Xu
2003-06-22  3:43                 ` Martin J. Bligh [this message]
2003-06-22  4:24                 ` Paul Mackerras
2003-06-22  8:32                   ` Geert Uytterhoeven
2003-06-22 13:34                     ` Daniel Phillips
2003-06-22  5:39                 ` gcc 3.3: largest *and* smallest kernels (was Re: [PATCH] Isapnp warning) Barry K. Nathan
2003-06-22 11:31                   ` Alan Cox
2003-06-22 13:22                 ` GCC speed (was " Daniel Phillips
2003-06-22 17:32                   ` Andrew Morton
2003-06-22 17:56                     ` Linus Torvalds
2003-06-22 18:58                     ` Henning P. Schmiedehausen
2003-06-22 19:12                       ` Sam Ravnborg
2003-06-22 19:13                       ` Andrew Morton
2003-06-22 19:32                         ` Henning Schmiedehausen
2003-06-22 19:51                       ` Adrian Bunk
2003-06-22 19:12                     ` Daniel Phillips
2003-06-23  1:05                     ` Larry McVoy
2002-01-04 11:32                       ` Pavel Machek
2003-07-17 10:18                         ` Christoph Hellwig
2003-07-17 10:23                           ` Jakub Jelinek
2003-07-17 10:27                             ` Christoph Hellwig
2003-06-22  8:49               ` [PATCH] Isapnp warning Russell King
2003-06-22  8:39             ` Jörn Engel
2003-06-22 14:07   ` Daniel Phillips
2003-06-22 15:00     ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2003-08-29 14:49 Geert Uytterhoeven
2003-06-15 19:10 Geert Uytterhoeven
2003-06-09 10:37 Geert Uytterhoeven

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='90770000.1056253431@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=acme@conectiva.com.br \
    --cc=akpm@digeo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).