[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1274217067.2485.9.camel@edumazet-laptop>
Date: Tue, 18 May 2010 23:11:07 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: mingo@...hat.com, linux-kernel@...r.kernel.org,
suresh.b.siddha@...el.com, tglx@...utronix.de, avi@...hat.com,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/fpu] x86: Add new static_cpu_has() function using
alternatives
Le mardi 18 mai 2010 à 13:57 -0700, H. Peter Anvin a écrit :
> On 05/18/2010 01:10 PM, Eric Dumazet wrote:
> > # gcc -v
> > Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
> > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> > --infodir=/usr/share/info --enable-shared --enable-threads=posix
> > --disable-checking --with-system-zlib --enable-__cxa_atexit
> > --disable-libunwind-exceptions --enable-java-awt=gtk
> > --host=i386-redhat-linux
> > Thread model: posix
> > gcc version 3.4.6 20060404 (Red Hat 3.4.6-10)
>
> I just implemented a fallback for gcc 3, but the real question is to
> which degree we still care about gcc 3 support for x86 specifically
> (other architectures might have other needs, but this is x86-specific code.)
>
> Lately the number of issues with gcc 3 support seems to have gone way
> up, and at some point we're going to have to cut it loose -- when would
> depend largely on what the usage case is; e.g. why are you, yourself,
> using gcc 3.4 to compile a state of the art kernel?
I use many different machines to compile kernels, and found this one
using gcc-3.4.6, but still running original 2.6.9.something RHEL
kernel ;)
For kernels I actually boot, I use gcc-4.5, 4.4.x, 4.3.x, 4.2.x, 4.1.2
(cross compiler)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists