From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
eric.dumazet@gmail.com, Ingo Molnar <mingo@elte.hu>, "Siddha\,
Suresh B" <suresh.b.siddha@intel.com>,
Thomas Gleixner <tglx@linutronix.de>, Avi Kivity <avi@redhat.com>
Subject: Re: Does anyone care about gcc 3.x support for *x86* anymore?
Date: Wed, 19 May 2010 07:08:19 -0700 [thread overview]
Message-ID: <4BF3F0D3.6070609@zytor.com> (raw)
In-Reply-To: <871vd8xb8t.fsf@basil.nowhere.org>
On 05/19/2010 06:38 AM, Andi Kleen wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>>
>> If there isn't a reason to preserve support, I would like to consider
>> discontinue support for using gcc 3 to compile x86 kernels. If there is
>> a valid use case, it would be good to know what it is.
>
> I suspect there are still distributions around that use it as a standard
> compiler. Wasn't it used in some major release of Debian?
>
> -Andi
There are, but that doesn't mean it's relevant for people to compile
bleeding-edge kernels with it.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-05-19 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 1:19 Does anyone care about gcc 3.x support for *x86* anymore? H. Peter Anvin
2010-05-19 7:13 ` Ingo Molnar
2010-05-19 13:38 ` Andi Kleen
2010-05-19 14:08 ` H. Peter Anvin [this message]
2010-05-19 22:45 ` Justin P. Mattock
2010-05-20 18:37 ` Martin Michlmayr
2010-05-20 19:56 ` Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2010-05-06 8:45 [PATCH v3 1/2] x86: eliminate TS_XSAVE Avi Kivity
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:57 ` H. Peter Anvin
2010-05-18 21:11 ` Eric Dumazet
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
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=4BF3F0D3.6070609@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.