From mboxrd@z Thu Jan 1 00:00:00 1970 From: "D. Hazelton" Subject: Re: [PATCH] KVM: 'asm' operand has impossible constraints Date: Sat, 27 Jan 2007 16:46:18 -0500 Message-ID: <200701271646.19067.dhazelton@enter.net> References: <200701260140.47760.caglar@pardus.org.tr> <45BB15F1.6020600@qumranet.com> <200701272328.31532.caglar@pardus.org.tr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Avi Kivity , lkml , kvm-devel@lists.sourceforge.net To: caglar@pardus.org.tr Return-path: In-Reply-To: <200701272328.31532.caglar@pardus.org.tr> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Saturday 27 January 2007 16:28, S.=C3=87a=C4=9Flar Onur wrote: > 27 Oca 2007 Cts tarihinde, Avi Kivity =C5=9Funlar=C4=B1 yazm=C4=B1=C5= =9Ft=C4=B1: > > The patch looks correct, but I don't understand the gcc error messa= ge. > > Are we sure this isn't a gcc 4.2 bug? > > > > "g" appears to be equivalent to "rmi", if "i" is impossible, gcc is= free > > to use "r" or "m", no? > > Accorgind to GCC devs. its not a bug > (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D29808), on comment #5 = the > problem described like; > > "g" means "r"+"i" so the register allocator in the -O0 case is select= ing > "r" while in the optimize case is selecting "i" Sounds like a bug to me! After all, shouldn't the different sections of= code=20 be selecting the *same* bits ? DRH