From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-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:34:59 -0700 [thread overview]
Message-ID: <4CC70333.80400@zytor.com> (raw)
In-Reply-To: <20101026123828.GA30434@basil.fritz.box>
On 10/26/2010 05:38 AM, Andi Kleen wrote:
> Hi,
>
> While doing a test run with the minimum supported compiler
> I found:
>
> An old gcc 3.3-hammer segfaults when compiling the current KVM
> emulate.c (or rather in x86_emulate_insns) on x86-64.
>
> The compiler goes into an endless recursion in validate_rtx and then
> eventually overflows the stack and dies.
>
> I minimized a test case, but didn't find a workaround
> (minimized test case http://halobates.de/emulate-min.i)
>
> My guess it's related to some of the inline assembler uses.
>
> This might be an excuse to bump the minimum compiler version again.
>
We have said 3.4 minimum for x86 for a long time now, and have an RFC
out to bump to 4.1. Unfortunately there isn't a good repo of
arch-specific version requirements in the kernel source code; in fact, I
just talked to Tony Luck yesterday about the need for that.
-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-10-26 16:35 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 [this message]
2010-10-26 16:37 ` Andi Kleen
2010-10-26 16:46 ` H. Peter Anvin
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=4CC70333.80400@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kvm@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