From: Mikael Pettersson <mikpe@csd.uu.se>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Arjan van de Ven <arjan@infradead.org>, Willy Tarreau <w@1wt.eu>,
Adrian Bunk <bunk@stusta.de>,
Willy Tarreau <wtarreau@hera.kernel.org>,
linux-kernel@vger.kernel.org, mtosatti@redhat.com,
Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: Linux 2.4.34-pre1
Date: Thu, 17 Aug 2006 10:50:43 +0200 [thread overview]
Message-ID: <17636.11747.89849.992490@alkaid.it.uu.se> (raw)
In-Reply-To: <44E42A4C.4040100@domdv.de>
Andreas Steinmetz writes:
> Arjan van de Ven wrote:
> > But maybe it's worth doing a user survey to find out what the users of
> > 2.4 want... (and with that I mean users of the kernel.org 2.4 kernels,
> > people who use enterprise distro kernels don't count for this since
> > they'll not go to a newer released 2.4 anyway)
>
> Currently I'm working with ARM based embedded systems. I prefer 2.4
> kernels to 2.6 as they are smaller thus leaving more flash for jffs2.
> Not speaking of the kernel a gcc 4.1.1 compile of code for a LPC2103
> resulted in a clearly smaller binary as the same compile with gcc 3.4.
> Thus I really would like to be able to use gcc 4.x with 2.4 kernels.
> There are even kernel miscompiles with gcc 3.4 that might be fixed with
> gcc 4 (one has to try).
I've done a fair amount of ARM user-space hacking recently, and the
number of bug fixes one has to apply to gcc-3.3 or gcc-3.4 to make it
even semi-correct on ARM is scary. Since these versions aren't supported
any more, being able to use newer, hopefully less buggy, and _supported_
gcc versions is clearly beneficial.
Of course, this is not an issue for x86 users.
next prev parent reply other threads:[~2006-08-17 8:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 22:36 Willy Tarreau
2006-08-16 23:54 ` Adrian Bunk
2006-08-17 5:16 ` Willy Tarreau
2006-08-17 6:48 ` Arjan van de Ven
2006-08-17 8:35 ` Andreas Steinmetz
2006-08-17 8:50 ` Mikael Pettersson [this message]
2006-08-17 12:48 ` Adrian Bunk
2006-08-17 20:43 ` Willy Tarreau
2006-08-17 23:41 ` Gerd v. Egidy
2006-08-18 4:40 ` Willy Tarreau
2006-08-21 0:56 ` Adrian Bunk
2006-08-17 9:06 ` Adrian Bunk
2006-08-17 9:16 ` Andreas Steinmetz
2006-08-18 23:25 ` Adrian Bunk
2006-08-19 1:20 ` Grant Coady
2006-08-20 17:27 ` Adrian Bunk
2006-08-19 4:45 ` Willy Tarreau
2006-08-21 0:35 ` Adrian Bunk
2006-08-21 0:41 ` Willy Tarreau
2006-08-21 1:07 ` Adrian Bunk
2006-08-17 8:37 ` Willy Tarreau
2006-08-17 9:12 ` Thomas Voegtle
2006-08-18 22:48 ` Solar Designer
2006-08-18 23:11 ` Adrian Bunk
2006-08-18 23:27 ` Solar Designer
2006-08-17 7:57 Chris Rankin
2006-08-17 9:16 ` Thomas Backlund
2006-08-18 4:47 ` Willy Tarreau
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=17636.11747.89849.992490@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=arjan@infradead.org \
--cc=ast@domdv.de \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mtosatti@redhat.com \
--cc=w@1wt.eu \
--cc=wtarreau@hera.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®