From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: "O.Sezer" <sezeroz@ttnet.net.tr>, Adrian Bunk <bunk@fs.tum.de>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.28-pre2
Date: Fri, 27 Aug 2004 09:00:20 -0300 [thread overview]
Message-ID: <20040827120020.GC32707@logos.cnet> (raw)
In-Reply-To: <20040826222622.GD564@alpha.home.local>
On Fri, Aug 27, 2004 at 12:26:22AM +0200, Willy Tarreau wrote:
> On Thu, Aug 26, 2004 at 10:50:03PM +0300, O.Sezer wrote:
> > >They are not a real problem with gcc 3.4, and whether gcc 3.5 will ever
> > >be supported as compiler for kernel 2.4 is a question whose answer lies
> > >far in the future.
> >
> > That is a valid point but it'd be sad if gcc3.5 wouldn't be supported.
>
> Tell that to gcc developpers who constantly break compatibility between
> versions. I even have userland programs which do not compile anymore with
> gcc-3.3 and which I don't even know how to 'fix' (workaround ?).
I dont care much about having gcc 3.5 work on v2.4 right now. Right now I think
we wont ever care about supporting it.
gcc 3.4 is more a of a concern because there is demand for it - Mikael has been
maintaining the patches out-of-the-tree for sometime now and I received
quite some reports about them (ie there is pressure for that).
But, due to the v2.4 state of life (bugfix mode only), I've been very annoyed
by these patches already. Uninliningfunctions is the most annoying thing
to me.
It doenst make sense for it (v2.4) to work on new-shiny-gcc next generation, v2.6/2.7
are there to support those.
next prev parent reply other threads:[~2004-08-27 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 15:26 Linux 2.4.28-pre2 O.Sezer
2004-08-26 19:15 ` Adrian Bunk
2004-08-26 19:50 ` O.Sezer
2004-08-26 22:26 ` Willy Tarreau
2004-08-27 12:00 ` Marcelo Tosatti [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 1:01 Marcelo Tosatti
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=20040827120020.GC32707@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sezeroz@ttnet.net.tr \
--cc=willy@w.ods.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