virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: virtualization@lists.osdl.org, "H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Paravirt compile failure with gcc33
Date: Wed, 10 Feb 2010 10:38:01 -0800	[thread overview]
Message-ID: <4B72FD09.1020202@goop.org> (raw)
In-Reply-To: <alpine.LSU.2.01.1002101909560.29808@obet.zrqbmnf.qr>

On 02/10/2010 10:13 AM, Jan Engelhardt wrote:
> As I was compile-testing 2.6.33-rc with gcc-3.3,
> binutils-2.19.51-10.26.4.x86_64, I observed a failure when
> CONFIG_PARAVIRT is turned on:
>    

Yeah, there's a gcc bug of some kind there, and its very hard to see how 
to work around it.  When we last discussed this, I think we were close 
to deciding to obsolete gcc 3.3.

HPA, do you remember?

     J

>
> [any file]
> /home/jengelh/code/linux/arch/x86/include/asm/paravirt.h: In function
> `rif_seq_stop':
> /home/jengelh/code/linux/arch/x86/include/asm/paravirt.h:763: warning:
> asm operand 5 probably doesn't match constraints
> /home/jengelh/code/linux/arch/x86/include/asm/paravirt.h:858: warning:
> asm operand 2 probably doesn't match constraints
> /home/jengelh/code/linux/arch/x86/include/asm/paravirt.h:763: error:
> impossible constraint in `asm'
> /home/jengelh/code/linux/arch/x86/include/asm/paravirt.h:858: error:
> impossible constraint in `asm'
>
> Disabling either PARAVIRT or using GCC4.x works around this.
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/virtualization
>
>    

  reply	other threads:[~2010-02-10 18:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 18:13 Paravirt compile failure with gcc33 Jan Engelhardt
2010-02-10 18:38 ` Jeremy Fitzhardinge [this message]
2010-02-10 18:41   ` H. Peter Anvin
2010-02-10 19:20   ` Jan Engelhardt
2010-02-10 21:08     ` 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=4B72FD09.1020202@goop.org \
    --to=jeremy@goop.org \
    --cc=hpa@zytor.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).