mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ahmed Masud" <masud@googgun.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>,
	"'John Jasen'" <jjasen1@umbc.edu>
Cc: "'J Sloan'" <jjs@pobox.com>, <lgb@lgb.hu>,
	"'Arjan van de Ven'" <arjanv@redhat.com>,
	<linux-kernel@vger.kernel.org>
Subject: RE: Which gcc version?
Date: Tue, 27 Nov 2001 03:42:22 -0500	[thread overview]
Message-ID: <000501c1771f$72f0cdc0$8604a8c0@googgun.com> (raw)
In-Reply-To: <E168QXg-00069p-00@the-village.bc.nu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> > That said, the versions in 7.1, and the patches available have
> > done  reasonably well for everything that I've tried to compile
> > (kernels  included).
> > 
> > What are they going to do about gcc 3.0.x? It'll be amusing 
> to watch.
> 
> Its shipped as an additional compiler as well. The only real 
> question now is how long before 3.x becomes really solid. 
> That should be in time for the next RH major update I hope

In case this is pertinent: I have been using gcc 3.0.2 since its
inception to compile the kernel on various CPUs (Pentium II, Pentium
III, AMD Athelon, and also the experimental stuff for PA/RISC 2.0)
and have not had any trouble with it.   Seems to be fairly solid and
trouble free.  RH has to get its act together though ... The gcc 2.96
and a kgcc for the kernel was just too hilarious and rather sad at
the same time.

Cheers.

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPANR7eA+WVFT6/r4EQK/OwCg+X2va7QIzbwDvRBv27Kf/AXmy3UAn1/h
AvFgqGDvS0iv7RQXMprUIJB8
=Hs5v
-----END PGP SIGNATURE-----


  reply	other threads:[~2001-11-27  8:48 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 12:53 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 [this message]
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
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='000501c1771f$72f0cdc0$8604a8c0@googgun.com' \
    --to=masud@googgun.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjanv@redhat.com \
    --cc=jjasen1@umbc.edu \
    --cc=jjs@pobox.com \
    --cc=lgb@lgb.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®