public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Daniel Phillips <phillips@bonn-fries.net>, war <war@starband.net>,
	Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Which gcc version?
Date: Fri, 23 Nov 2001 12:35:12 -0800	[thread overview]
Message-ID: <3BFEB300.680A55A7@zip.com.au> (raw)
In-Reply-To: <3BFEAE22.1CE8DE5B@zip.com.au>, <5.1.0.14.2.20011123135801.00aad970@pop.cus.cam.ac.uk> <5.1.0.14.2.20011123185333.00afd920@pop.cus.cam.ac.uk> <5.1.0.14.2.20011123185333.00afd920@pop.cus.cam.ac.uk> <E167M0I-0002PD-00@starship.berlin> <5.1.0.14.2.20011123201824.05610ec0@pop.cus.cam.ac.uk>

Anton Altaparmakov wrote:
> 
> Hi Andrew,
> 
> At 20:14 23/11/01, Andrew Morton wrote:
> >Daniel Phillips wrote:
> > >
> > > If there is a performance hit, it's not enough to worry about.
> >
> >except egcs-1.1.2 (2.91.6) compiles stuff at almost twice the speed
> >of gcc3.  The person who breaks egcs-1.1.2 for kernel builds owes
> >me a quad Xeon, thanks very much.
> 
> Have you read the current Documentation/Changes? It says "the 2.5 tree is
> likely to drop egcs-1.1.2 workarounds". Whoever wrote that seems to be
> wanting to break it in the near future...

Well that's great news.  To whom do I send my shipping address?

Actually, I have negligible interest in working on something which
won't be useful to real people for three years, so that works out,
doesn't it?

-

  reply	other threads:[~2001-11-23 20:36 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 12:53 Which gcc version? Roy Sigurd Karlsbakk
2001-11-23 12:57 ` Arjan van de Ven
2001-11-23 13:51 ` war
2001-11-23 19:43   ` J Sloan
2001-11-23 13:59 ` Anton Altaparmakov
2001-11-23 14:11   ` war
2001-11-23 15:14     ` Arjan van de Ven
2001-11-23 15:30       ` Gábor Lénárt
2001-11-23 15:34         ` Arjan van de Ven
2001-11-23 17:13         ` Re[2]: " Nerijus Baliunas
2001-11-23 19:50         ` J Sloan
2001-11-23 20:34           ` John Jasen
2001-11-23 21:55             ` J Sloan
2001-11-24  3:08               ` John Jasen
2001-11-24 12:24             ` Paul G. Allen
2001-11-26 18:31             ` Alan Cox
2001-11-27  8:42               ` Ahmed Masud
2001-11-23 16:10       ` Anton Altaparmakov
2001-11-23 14:43   ` Anton Altaparmakov
2001-11-23 16:23     ` Jeff Garzik
2001-11-23 18:30   ` Daniel Phillips
2001-11-23 18:56   ` Anton Altaparmakov
2001-11-23 19:28     ` Daniel Phillips
2001-11-23 20:14       ` Andrew Morton
2001-11-23 20:24       ` Anton Altaparmakov
2001-11-23 20:35         ` Andrew Morton [this message]
2001-11-23 21:09           ` David Weinehall
2001-11-24 16:01     ` Luigi Genoni
2001-11-24 16:09       ` Daniel Phillips
2001-11-24 17:32         ` Luigi Genoni
  -- strict thread matches above, loose matches on Subject: below --
2001-11-23 17:12 RaúlNúñez de Arenas Coronado
2001-11-23 18:02 ` M. Edward (Ed) Borasky
2001-11-23 18:14   ` Thorsten Glaser
2001-04-05 10:56 which " Manoj Sontakke
2001-04-05  5:48 ` Alexander Viro
2001-04-05 14:09   ` Manoj Sontakke
2001-04-05 11:37     ` Bart Trojanowski
2001-04-05 12:02       ` Matti Aarnio
2001-04-05 12:26       ` David Woodhouse
2001-04-05 12:31         ` Matti Aarnio
2001-04-05 13:09         ` Richard B. Johnson
2001-04-05 11:45     ` Matti Aarnio
2001-04-05 11:50     ` christophe barbe

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=3BFEB300.680A55A7@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    --cc=roy@karlsbakk.net \
    --cc=war@starband.net \
    /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