From: Avi Kivity <avi@qumranet.com>
To: Bernhard Rosenkraenzer <bero@arklinux.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.19-rc5-mm1 fails to compile with gcc 4.2
Date: Sun, 12 Nov 2006 11:24:48 +0200 [thread overview]
Message-ID: <4556E860.700@qumranet.com> (raw)
In-Reply-To: <200611121005.58939.bero@arklinux.org>
Bernhard Rosenkraenzer wrote:
> On Sunday, 12. November 2006 09:22, Avi Kivity wrote:
>
>> Bernhard Rosenkraenzer wrote:
>>
>>> drivers/kvm/kvm_main.c: In function 'kvm_dev_ioctl_run':
>>> drivers/kvm/kvm_main.c:153: error: 'asm' operand has impossible
>>> constraints drivers/kvm/kvm_main.c:158: error: 'asm' operand has
>>> impossible constraints
>>>
>> Smells like a gcc regression. Can you send .config?
>>
>> Or better yet, preprocessed source and full gcc command line (as seen on
>> 'make V=1').
>>
>
> It does look like a gcc bug -- -O0 makes it go away.
> Details at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29808
>
That's a different bug, gcc generates code that the assembler can't
handle. Might be an assembler bug.
Can you compile it with -S and post the generated assembly?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2006-11-12 9:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-11 22:34 2.6.19-rc5-mm1 fails to compile with gcc 4.2 Bernhard Rosenkraenzer
2006-11-12 8:22 ` Avi Kivity
2006-11-12 9:05 ` Bernhard Rosenkraenzer
2006-11-12 9:24 ` Avi Kivity [this message]
2006-11-12 13:36 ` Bernhard Rosenkraenzer
2006-11-12 13:43 ` Avi Kivity
2006-11-12 13:50 ` Bernhard Rosenkraenzer
2006-11-12 13:55 ` Avi Kivity
2006-11-12 14:13 ` Segher Boessenkool
2006-11-12 14:10 ` Segher Boessenkool
2006-11-12 11:17 ` Segher Boessenkool
2006-11-12 13:43 ` Bernhard Rosenkraenzer
2006-11-12 13:50 ` Avi Kivity
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=4556E860.700@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=bero@arklinux.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 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.