From: Willy Tarreau <willy@w.ods.org>
To: Adam Heath <doogie@debian.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Chris Wedgwood <cw@f00f.org>,
Christoph Hellwig <hch@infradead.org>,
Timothy Miller <miller@techsource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: support of older compilers
Date: Fri, 5 Nov 2004 21:20:38 +0100 [thread overview]
Message-ID: <20041105202038.GC30993@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.58.0411041734100.1229@gradall.private.brainfood.com>
On Thu, Nov 04, 2004 at 05:39:08PM -0600, Adam Heath wrote:
> Using an old version of gcc because it is faster at compiling is a
> non-argument.
If you can send to all of us for free some hardware which is twice as fast
as what we have, which does not generate more heat and noise, then perhaps
most of us will accept to use a twice as slow compiler. But not for long,
since some may realize that they can produce quality code twice as fast on
their new system ;-)
At least, with fast machines and fast compilers, people have no excuse not
testing the patches they send. A few years ago, broken & non-tested patches
were very common. This could become standard again if everyone jumped into
gcc 3.4 unconditionnaly.
> If they produce bad code, then that's a valid reason.
> If they produce larger code, that is a valid reason.
You can also ask the gcc people when they will decide to write a new version
which is able to compile some code which compiles with the previous release.
I have some tools which don't compile anymore with gcc 3 and error messages
look more like insults than information, and I don't even know how to "fix"
(adapt ?) them. This too is a valid reason to stick to older compilers.
Willy
next prev parent reply other threads:[~2004-11-05 20:25 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 21:02 support of older compilers Timothy Miller
2004-11-03 21:13 ` Christoph Hellwig
2004-11-03 21:22 ` Chris Wedgwood
2004-11-03 23:06 ` Adam Heath
2004-11-03 23:30 ` Chris Wedgwood
2004-11-04 16:50 ` Adam Heath
2004-11-04 17:00 ` Chris Friesen
2004-11-04 18:17 ` Adam Heath
2004-11-05 20:00 ` Willy Tarreau
2004-11-05 20:28 ` Geert Uytterhoeven
2004-11-05 20:31 ` Willy Tarreau
2004-11-04 17:04 ` Valdis.Kletnieks
2004-11-04 18:15 ` Adam Heath
2004-11-04 18:31 ` Valdis.Kletnieks
2004-11-04 21:56 ` Adam Heath
2004-11-04 18:54 ` Ian Romanick
2004-11-04 19:48 ` Christoph Hellwig
2004-11-04 20:14 ` Giuseppe Bilotta
2004-11-05 20:04 ` Willy Tarreau
2004-11-04 19:36 ` Ian Hastie
2004-11-04 20:02 ` Ioan Ionita
2004-11-04 20:03 ` Adrian Bunk
2004-11-04 20:08 ` Valdis.Kletnieks
2004-11-04 19:38 ` Linus Torvalds
2004-11-04 21:47 ` Adam Heath
2004-11-04 21:55 ` Linus Torvalds
2004-11-04 23:39 ` Adam Heath
2004-11-04 23:52 ` Linus Torvalds
2004-11-05 1:41 ` Andries Brouwer
2004-11-05 15:41 ` Linus Torvalds
2004-11-05 15:47 ` Arjan van de Ven
2004-11-05 16:22 ` linux-os
2004-11-05 19:50 ` Chris Wedgwood
2004-11-05 20:28 ` Linus Torvalds
2004-11-05 21:59 ` Grzegorz Kulewski
2004-11-05 22:08 ` Linus Torvalds
2004-11-05 23:02 ` [PATCH] change Kconfig entry for RAMFS (Was: Re: support of older compilers) Grzegorz Kulewski
2004-11-05 23:12 ` Linus Torvalds
2004-11-05 23:44 ` [PATCH] change Kconfig entry for RAMFS Grzegorz Kulewski
2004-11-06 0:48 ` Grzegorz Kulewski
2004-11-09 23:24 ` Matt Mackall
2004-11-10 10:40 ` Grzegorz Kulewski
2004-11-10 20:50 ` Bill Davidsen
2004-11-05 23:27 ` [PATCH] change Kconfig entry for RAMFS (Was: Re: support of older compilers) DaMouse
2004-11-05 23:49 ` Grzegorz Kulewski
2004-11-06 13:59 ` DaMouse
2004-11-05 22:08 ` support of older compilers Hua Zhong
2004-11-06 8:38 ` Willy Tarreau
2004-11-06 9:43 ` Hugh Dickins
2004-11-06 11:04 ` Willy Tarreau
2004-11-05 22:37 ` support of older compilers [u] Martin Schlemmer [c]
2004-11-05 23:14 ` Grzegorz Kulewski
2004-11-05 23:38 ` chibiryuu
2004-11-06 12:07 ` support of older compilers Andries Brouwer
2004-11-06 17:33 ` Linus Torvalds
2004-11-06 19:36 ` Adrian Bunk
2004-11-06 21:41 ` bloat Andries Brouwer
2004-11-06 22:07 ` bloat Adrian Bunk
2004-11-06 21:30 ` bloat Arnaldo Carvalho de Melo
2004-11-07 13:37 ` bloat Frank van Maarseveen
2004-11-05 20:20 ` Willy Tarreau [this message]
2004-11-05 22:19 ` support of older compilers Adam Heath
2004-11-04 22:36 ` Martin J. Bligh
2004-11-04 20:48 ` Bill Davidsen
2004-11-04 22:33 ` Martin J. Bligh
2004-11-03 21:17 ` Matti Aarnio
2004-11-03 21:37 ` Giacomo A. Catenazzi
2004-11-03 21:57 ` Valdis.Kletnieks
2004-11-04 2:16 ` Miles Bader
2004-11-03 22:07 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2004-11-04 19:33 Clayton Weaver
2004-11-05 15:36 ` Nix
2004-11-04 22:49 Xose Vazquez Perez
2004-11-06 9:07 Clayton Weaver
2004-11-09 17:39 ` Nix
[not found] <2Xj2s-5vj-33@gated-at.bofh.it>
2004-11-06 10:15 ` Anton Ertl
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=20041105202038.GC30993@alpha.home.local \
--to=willy@w.ods.org \
--cc=cw@f00f.org \
--cc=doogie@debian.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.