From: "H. Peter Anvin" <hpa@zytor.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
suresh.b.siddha@intel.com, tglx@linutronix.de, avi@redhat.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/fpu] x86: Add new static_cpu_has() function using alternatives
Date: Tue, 18 May 2010 13:57:10 -0700 [thread overview]
Message-ID: <4BF2FF26.9050701@zytor.com> (raw)
In-Reply-To: <1274213443.2485.3.camel@edumazet-laptop>
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?
-hpa
next prev parent reply other threads:[~2010-05-18 20:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 8:45 [PATCH v3 0/2] x86 FPU API Avi Kivity
2010-05-06 8:45 ` [PATCH v3 1/2] x86: eliminate TS_XSAVE Avi Kivity
2010-05-10 20:39 ` [tip:x86/fpu] x86: Eliminate TS_XSAVE tip-bot for Avi Kivity
2010-05-12 0:18 ` [tip:x86/fpu] x86, fpu: Use the proper asm constraint in use_xsave() tip-bot for H. Peter Anvin
2010-05-12 1:06 ` [tip:x86/fpu] x86: Add new static_cpu_has() function using alternatives tip-bot for H. Peter Anvin
2010-05-18 20:10 ` Eric Dumazet
2010-05-18 20:43 ` H. Peter Anvin
2010-05-18 20:57 ` H. Peter Anvin [this message]
2010-05-18 21:11 ` Eric Dumazet
2010-05-18 21:31 ` H. Peter Anvin
2010-05-18 21:38 ` Does anyone care about gcc 3.x support for x86 anymore? H. Peter Anvin
2010-05-19 23:10 ` Mauro Carvalho Chehab
2010-05-20 0:39 ` H. Peter Anvin
2010-05-20 0:42 ` H. Peter Anvin
2010-05-20 12:44 ` Ingo Molnar
2010-05-18 20:58 ` [tip:x86/fpu] x86: Add new static_cpu_has() function using alternatives H. Peter Anvin
2010-05-18 21:31 ` Eric Dumazet
2010-05-27 20:12 ` [tip:x86/urgent] x86, cpufeature: Unbreak compile with gcc 3.x tip-bot for H. Peter Anvin
2010-05-12 1:06 ` [tip:x86/fpu] x86, fpu: Use static_cpu_has() to implement use_xsave() tip-bot for H. Peter Anvin
2010-05-06 8:45 ` [PATCH v3 2/2] x86: Introduce 'struct fpu' and related API Avi Kivity
2010-05-10 20:39 ` [tip:x86/fpu] " tip-bot for Avi Kivity
2010-05-10 20:40 ` [tip:x86/fpu] x86, fpu: Unbreak FPU emulation tip-bot for H. Peter Anvin
2010-05-10 8:48 ` [PATCH v3 0/2] x86 FPU API Avi Kivity
2010-05-10 15:24 ` H. Peter Anvin
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=4BF2FF26.9050701@zytor.com \
--to=hpa@zytor.com \
--cc=avi@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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.