From: "Zeev Tarantov" <zeev.tarantov@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] fix for TEST_BSX in test-i386.c
Date: Sat, 13 Sep 2008 01:06:14 +0300 [thread overview]
Message-ID: <12d7e64c0809121506u5e90c121vfda353321c227c9d@mail.gmail.com> (raw)
Hello!
In GCC 4.3.1 I get syntax errors building test-i386.c with any
optimization level higher than -O0.
I assume this does not happen with GCC 3.X.
The following patch fixes the problem. I believe that it is more
correct and not just a quirk of gcc.
After applying this, the tests produce expected results (and pass).
If this is a double post, I apologize - I have tried sending this
using gmane without being subscribed to the list.
--- tests/test-i386.c (revision 5200)
+++ tests/test-i386.c (working copy)
@@ -716,8 +716,8 @@
asm("xor %1, %1\n"\
"mov $0x12345678, %0\n"\
#op " %" size "2, %" size "0 ; setz %b1" \
- : "=r" (res), "=q" (resz)\
- : "g" (val));\
+ : "=&r" (res), "=&q" (resz)\
+ : "r" (val));\
printf("%-10s A=" FMTLX " R=" FMTLX " %ld\n", #op, val, res, resz);\
}
-Zeev
reply other threads:[~2008-09-12 22:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=12d7e64c0809121506u5e90c121vfda353321c227c9d@mail.gmail.com \
--to=zeev.tarantov@gmail.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).