From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] kvm-unittest: fix build with gcc 4.3.X and older
Date: Thu, 17 Oct 2013 11:27:37 +0300 [thread overview]
Message-ID: <20131017082737.GA14218@redhat.com> (raw)
In-Reply-To: <20131017082027.GA16998@redhat.com>
On Thu, Oct 17, 2013 at 11:20:27AM +0300, Gleb Natapov wrote:
> On Thu, Oct 17, 2013 at 11:12:31AM +0300, Michael S. Tsirkin wrote:
> > On Thu, Oct 17, 2013 at 09:27:51AM +0300, Gleb Natapov wrote:
> > > 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.
> >
> > Well it's not as widely used as kvm itself yet :)
> > The patch seems simple enough though.
> >
> > > 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'
> >
> > OK that's easy to fix.
> >
> > > > 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.
> >
> > It does produce warnings with -Wall though:
> > Assembler messages:
> > Warning: using `%ax' instead of `%eax' due to `w' suffix
> > Warning: using `%al' instead of `%eax' due to `b' suffix
> >
> Not for me. No warning with 4.7.3 and 4.2. .s file produced by gcc shows
> correct assembly with my patch.
4.3 doesn't.
We have the "a" constraint there anyway - so what's the issue with just
writing %eax etc? I think it's safer than relying on compiler to do
the right thing.
> --
> Gleb.
next prev parent reply other threads:[~2013-10-17 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 19:46 [Qemu-devel] [PATCH] kvm-unittest: fix build with gcc 4.3.X and older Michael S. Tsirkin
2013-10-17 6:27 ` Gleb Natapov
2013-10-17 8:12 ` Michael S. Tsirkin
2013-10-17 8:20 ` Gleb Natapov
2013-10-17 8:27 ` Michael S. Tsirkin [this message]
2013-10-17 8:34 ` Gleb Natapov
2013-10-17 9:28 ` Michael S. Tsirkin
2013-10-17 9:33 ` Gleb Natapov
2013-10-17 9:44 ` Michael S. Tsirkin
2013-10-17 9:43 ` Gleb Natapov
2013-10-17 10:55 ` Paolo Bonzini
2013-10-17 10:58 ` Gleb Natapov
2013-10-17 11:02 ` Paolo Bonzini
2013-10-17 11:31 ` Michael S. Tsirkin
2013-10-17 10:53 ` Paolo Bonzini
2013-10-17 11:29 ` 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=20131017082737.GA14218@redhat.com \
--to=mst@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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 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).