public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Georgalis <george@galis.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Recommended compiler version
Date: Sat, 29 May 2004 21:18:46 -0400	[thread overview]
Message-ID: <20040530011846.GA5975@trot.local> (raw)
In-Reply-To: <200405291457.i4TEvtcn000170@81-2-122-30.bradfords.org.uk>

On Sat, May 29, 2004 at 03:57:55PM +0100, John Bradford wrote:
>Quote from Adrian Bunk <bunk@fs.tum.de>:
>> Whether support for gcc 2.95 should be dropped is a discussion for 2.7.
>
>Is there any single 3.x.x version of GCC that's actively in use by a large
>number of core developers?  How do we make a sensible recommendation if not?

I've used gcc-3.3.2, since about when it came out. It's been reliable
for me so I haven't noticed/tried newer versions. A few times I had
problems, with xfree or mplayer and reverted to my distro version:
gcc version 2.95.4 20011002 (Debian prerelease)

if a standard, by someone more experienced with c than myself, where
used that indicated preferred, known.works, known.broken versions of
gcc, then developers could maintain the information, for their code,
in a way that would make it easy to make global assertions on what gcc
version is preferred, works or broken. Plus, make errors that say "this
doesn't work with that gcc version" could save a lot of headaches.

// George


-- 
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/  cell:646-331-2027  mailto:george@galis.org
Key fingerprint = 5415 2738 61CF 6AE1 E9A7  9EF0 0186 503B 9831 1631


  reply	other threads:[~2004-05-30  1:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29  9:16 Recommended compiler version Francois Romieu
2004-05-29  9:52 ` Francois Romieu
2004-05-29 13:30   ` John Bradford
2004-05-29 14:12     ` Francois Romieu
2004-05-29 14:31       ` Adrian Bunk
2004-05-29 14:57         ` John Bradford
2004-05-30  1:18           ` George Georgalis [this message]
2004-05-29 14:53       ` John Bradford
2004-05-29 16:58         ` Francois Romieu
     [not found] <218aB-15c-17@gated-at.bofh.it>
2004-05-29 10:51 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2004-05-29 14:42 Dan Kegel
2004-05-29 23:55 ` Karim Yaghmour
2004-05-29 23:20   ` Dan Kegel
2004-05-30  0:40     ` Karim Yaghmour
2004-05-30  0:38   ` Karim Yaghmour
2004-05-30 10:37 ` John Bradford

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=20040530011846.GA5975@trot.local \
    --to=george@galis.org \
    --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