All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] kvm-unittest: fix build with gcc 4.3.X and older
Date: Thu, 17 Oct 2013 12:55:16 +0200	[thread overview]
Message-ID: <525FC214.4020501@redhat.com> (raw)
In-Reply-To: <20131017062751.GK15657@redhat.com>

Il 17/10/2013 08:27, Gleb Natapov ha scritto:
> On Wed, Oct 16, 2013 at 10:46:53PM +0300, Michael S. Tsirkin wrote:
>> Old GCC didn't let you reference variable by
>> number if it is listed with a specific register
>> constraint, on the assumption you can just
>> use the register name explicitly.
>>
>> Build fails with errors like this:
>> a.c:6: error: invalid 'asm': invalid operand code 'd'
>>
> Is it worth to support such ancient compiler? Nobody complained till
> now. BTW with your patch I still cannot compile with 4.2:
> 
> x86/s3.c: In function 'main':
> x86/s3.c:145: error: inconsistent operand constraints in an 'asm'
> 
>> To fix, let's just use %eax %al etc.
>>
> Only %d0 does not work and dropping "d" fixes it since compiler can
> figure out correct register from variable size. The patch bellow fixes
> compilation for 4.2.
>  
> diff --git a/lib/x86/pci.c b/lib/x86/pci.c
> index f95cd88..231668a 100644
> --- a/lib/x86/pci.c
> +++ b/lib/x86/pci.c
> @@ -3,13 +3,13 @@
>  
>  static void outl(unsigned short port, unsigned val)
>  {
> -    asm volatile("outl %d0, %w1" : : "a"(val), "Nd"(port));
> +    asm volatile("outl %0, %w1" : : "a"(val), "Nd"(port));
>  }
>  
>  static unsigned inl(unsigned short port)
>  {
>      unsigned data;
> -    asm volatile("inl %w1, %d0" : "=a"(data) : "Nd"(port));
> +    asm volatile("inl %w1, %0" : "=a"(data) : "Nd"(port));
>      return data;
>  }

This is okay.

>  static uint32_t pci_config_read(pcidevaddr_t dev, uint8_t reg)
> diff --git a/x86/s3.c b/x86/s3.c
> index 71d3ff9..d568aa7 100644
> --- a/x86/s3.c
> +++ b/x86/s3.c
> @@ -143,14 +143,14 @@ static inline int rtc_in(u8 reg)
>  {
>      u8 x = reg;
>      asm volatile("outb %b1, $0x70; inb $0x71, %b0"
> -		 : "+a"(x) : "0"(x));
> +		 : "=a"(x) : "0"(x));
>      return x;
>  }

This should be wrong.  GCC should complain that the same operand is used
for both input and output but has an "=" constraint.

>  static inline void rtc_out(u8 reg, u8 val)
>  {
>      asm volatile("outb %b1, $0x70; mov %b2, %b1; outb %b1, $0x71"
> -		 : "+a"(reg) : "0"(reg), "ri"(val));
> +		 : "=a"(reg) : "0"(reg), "ri"(val));
>  }

Same here.

But I'm not sure what is the error message for older GCC for s3.c, as I
wrote in reply to Michael.

>  extern char resume_start, resume_end;
> diff --git a/x86/vmexit.c b/x86/vmexit.c
> index 3b945de..7e9af15 100644
> --- a/x86/vmexit.c
> +++ b/x86/vmexit.c
> @@ -26,7 +26,7 @@ static void outw(unsigned short port, unsigned val)
>  
>  static void outl(unsigned short port, unsigned val)
>  {
> -    asm volatile("outl %d0, %w1" : : "a"(val), "Nd"(port));
> +    asm volatile("outl %0, %w1" : : "a"(val), "Nd"(port));
>  }

Okay.

Paolo

>  static unsigned int inb(unsigned short port)
> --
> 			Gleb.
> 


WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] kvm-unittest: fix build with gcc 4.3.X and older
Date: Thu, 17 Oct 2013 12:55:16 +0200	[thread overview]
Message-ID: <525FC214.4020501@redhat.com> (raw)
In-Reply-To: <20131017062751.GK15657@redhat.com>

Il 17/10/2013 08:27, Gleb Natapov ha scritto:
> On Wed, Oct 16, 2013 at 10:46:53PM +0300, Michael S. Tsirkin wrote:
>> Old GCC didn't let you reference variable by
>> number if it is listed with a specific register
>> constraint, on the assumption you can just
>> use the register name explicitly.
>>
>> Build fails with errors like this:
>> a.c:6: error: invalid 'asm': invalid operand code 'd'
>>
> Is it worth to support such ancient compiler? Nobody complained till
> now. BTW with your patch I still cannot compile with 4.2:
> 
> x86/s3.c: In function 'main':
> x86/s3.c:145: error: inconsistent operand constraints in an 'asm'
> 
>> To fix, let's just use %eax %al etc.
>>
> Only %d0 does not work and dropping "d" fixes it since compiler can
> figure out correct register from variable size. The patch bellow fixes
> compilation for 4.2.
>  
> diff --git a/lib/x86/pci.c b/lib/x86/pci.c
> index f95cd88..231668a 100644
> --- a/lib/x86/pci.c
> +++ b/lib/x86/pci.c
> @@ -3,13 +3,13 @@
>  
>  static void outl(unsigned short port, unsigned val)
>  {
> -    asm volatile("outl %d0, %w1" : : "a"(val), "Nd"(port));
> +    asm volatile("outl %0, %w1" : : "a"(val), "Nd"(port));
>  }
>  
>  static unsigned inl(unsigned short port)
>  {
>      unsigned data;
> -    asm volatile("inl %w1, %d0" : "=a"(data) : "Nd"(port));
> +    asm volatile("inl %w1, %0" : "=a"(data) : "Nd"(port));
>      return data;
>  }

This is okay.

>  static uint32_t pci_config_read(pcidevaddr_t dev, uint8_t reg)
> diff --git a/x86/s3.c b/x86/s3.c
> index 71d3ff9..d568aa7 100644
> --- a/x86/s3.c
> +++ b/x86/s3.c
> @@ -143,14 +143,14 @@ static inline int rtc_in(u8 reg)
>  {
>      u8 x = reg;
>      asm volatile("outb %b1, $0x70; inb $0x71, %b0"
> -		 : "+a"(x) : "0"(x));
> +		 : "=a"(x) : "0"(x));
>      return x;
>  }

This should be wrong.  GCC should complain that the same operand is used
for both input and output but has an "=" constraint.

>  static inline void rtc_out(u8 reg, u8 val)
>  {
>      asm volatile("outb %b1, $0x70; mov %b2, %b1; outb %b1, $0x71"
> -		 : "+a"(reg) : "0"(reg), "ri"(val));
> +		 : "=a"(reg) : "0"(reg), "ri"(val));
>  }

Same here.

But I'm not sure what is the error message for older GCC for s3.c, as I
wrote in reply to Michael.

>  extern char resume_start, resume_end;
> diff --git a/x86/vmexit.c b/x86/vmexit.c
> index 3b945de..7e9af15 100644
> --- a/x86/vmexit.c
> +++ b/x86/vmexit.c
> @@ -26,7 +26,7 @@ static void outw(unsigned short port, unsigned val)
>  
>  static void outl(unsigned short port, unsigned val)
>  {
> -    asm volatile("outl %d0, %w1" : : "a"(val), "Nd"(port));
> +    asm volatile("outl %0, %w1" : : "a"(val), "Nd"(port));
>  }

Okay.

Paolo

>  static unsigned int inb(unsigned short port)
> --
> 			Gleb.
> 

  parent reply	other threads:[~2013-10-17 10:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 19:46 [PATCH] kvm-unittest: fix build with gcc 4.3.X and older Michael S. Tsirkin
2013-10-16 19:46 ` [Qemu-devel] " Michael S. Tsirkin
2013-10-17  6:27 ` Gleb Natapov
2013-10-17  6:27   ` [Qemu-devel] " Gleb Natapov
2013-10-17  8:12   ` Michael S. Tsirkin
2013-10-17  8:12     ` [Qemu-devel] " Michael S. Tsirkin
2013-10-17  8:20     ` Gleb Natapov
2013-10-17  8:20       ` [Qemu-devel] " Gleb Natapov
2013-10-17  8:27       ` Michael S. Tsirkin
2013-10-17  8:27         ` [Qemu-devel] " Michael S. Tsirkin
2013-10-17  8:34         ` Gleb Natapov
2013-10-17  8:34           ` [Qemu-devel] " Gleb Natapov
2013-10-17  9:28           ` Michael S. Tsirkin
2013-10-17  9:28             ` [Qemu-devel] " Michael S. Tsirkin
2013-10-17  9:33             ` Gleb Natapov
2013-10-17  9:33               ` [Qemu-devel] " Gleb Natapov
2013-10-17  9:44               ` Michael S. Tsirkin
2013-10-17  9:44                 ` [Qemu-devel] " Michael S. Tsirkin
2013-10-17  9:43                 ` Gleb Natapov
2013-10-17  9:43                   ` [Qemu-devel] " Gleb Natapov
2013-10-17 10:55   ` Paolo Bonzini [this message]
2013-10-17 10:55     ` Paolo Bonzini
2013-10-17 10:58     ` Gleb Natapov
2013-10-17 10:58       ` [Qemu-devel] " Gleb Natapov
2013-10-17 11:02       ` Paolo Bonzini
2013-10-17 11:02         ` [Qemu-devel] " Paolo Bonzini
2013-10-17 11:31         ` Michael S. Tsirkin
2013-10-17 11:31           ` [Qemu-devel] " Michael S. Tsirkin
2013-10-17 10:53 ` Paolo Bonzini
2013-10-17 10:53   ` [Qemu-devel] " Paolo Bonzini
2013-10-17 11:29   ` Michael S. Tsirkin
2013-10-17 11:29     ` [Qemu-devel] " Michael S. Tsirkin

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=525FC214.4020501@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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.