public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: kvm@vger.kernel.org, avi@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: fyi: gcc33-hammer crashes when compiling kvm emulate.c
Date: Tue, 26 Oct 2010 09:46:37 -0700	[thread overview]
Message-ID: <4CC705ED.1020105@zytor.com> (raw)
In-Reply-To: <20101026163748.GB29961@basil.fritz.box>

On 10/26/2010 09:37 AM, Andi Kleen wrote:
>> We have said 3.4 minimum for x86 for a long time now, and have an RFC
> 
> Ok makes sense. I thought it was still at 3.3. I should retire
> this 3.3 fossil anyways, it's really only for old compat testing.
> 
> I don't remember seeing a warning -- aren't there supposed to be warnings
> for unsupported compilers?
> 

Not unless they are actively known to break.  People get huffy about it
because even if it is known to have problems it doesn't break *their*
particular configuration.  I'm getting to be of the opinion that people
who compile modern kernels with ancient compilers and expect it to work
are suffering from some particular kind of insanity -- it's nothing the
distros do.  The only exception are embedded people who compile with the
latest 3.4 gcc; they have explained they do so because newer gccs have
too many dependencies (the actual compiler, not the generated code) and
for speed.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-10-26 16:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 12:38 fyi: gcc33-hammer crashes when compiling kvm emulate.c Andi Kleen
2010-10-26 16:34 ` H. Peter Anvin
2010-10-26 16:37   ` Andi Kleen
2010-10-26 16:46     ` H. Peter Anvin [this message]
2010-10-26 17:01       ` Andi Kleen
2010-10-26 18:19         ` H. Peter Anvin
2010-10-26 20:27           ` Andi Kleen
2010-10-26 20:37             ` H. Peter Anvin
2010-10-27 10:50               ` Avi Kivity
2010-10-27 17:00                 ` Andi Kleen

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=4CC705ED.1020105@zytor.com \
    --to=hpa@zytor.com \
    --cc=andi@firstfloor.org \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.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