From: David Hildenbrand <david@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
"Thomas Huth" <thuth@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH RFC 1/2] tests/tcg: Allow targets to set the optimization level
Date: Wed, 27 Feb 2019 13:42:41 +0100 [thread overview]
Message-ID: <467f1311-0534-232d-b85d-2d6e0fd47661@redhat.com> (raw)
In-Reply-To: <87lg21lai8.fsf@zen.linaroharston>
On 27.02.19 12:46, Alex Bennée wrote:
>
> David Hildenbrand <david@redhat.com> writes:
>
>> We sometimes want basic optimizations, e.g. for constant propagation
>> into inlined functions.
>>
>> Especially for inline asm with immediates;
>
> I agree you need this, but...
>
> <snip>
>> # Start with a blank slate, the build targets get to add stuff first
>> -CFLAGS=
>> +CFLAGS=-O0
>> QEMU_CFLAGS=
>> LDFLAGS=
>>
>> @@ -70,7 +70,7 @@ ifneq ($(TARGET_BASE_ARCH),$(TARGET_NAME))
>> endif
>>
>> # Add the common build options
>> -CFLAGS+=-Wall -O0 -g -fno-strict-aliasing
>> +CFLAGS+=-Wall -g -fno-strict-aliasing
>
>
> You don't need to do this - we already have EXTRA_CFLAGS which will
> always be at the end of the compile invocation:
>
> # enable vectors and optimisation to vectorise for this test
> vglv: CFLAGS+=-march=z13 -m64
> vglv: EXTRA_CFLAGS+=-O2
For whatever reason I can't get this to work. EXTRA_CFLAGS+=-O2 is
always silently dropped:
make SHELL='sh -x' run-tcg-tests-s390x-linux-user
+ /home/dhildenb/git/qemu/tests/docker/docker.py cc --user 100813 --cc
s390x-linux-gnu-gcc -i qemu:debian-s390x-cross -s
/home/dhildenb/git/qemu -- -march=zEC12 -m64 -Wall -O0 -g
-fno-strict-aliasing -march=z13
/home/dhildenb/git/qemu/tests/tcg/s390x/vlgv.c -o vlgv -static
/home/dhildenb/git/qemu/tests/tcg/s390x/vlgv.c: In function 'vlgv':
/home/dhildenb/git/qemu/tests/tcg/s390x/vlgv.c:8:5: warning: asm operand
3 probably doesn't match constraints
asm volatile("vlgv %[r1], %[v3], 0(%[a2]), %[m4]\n"
^~~
/home/dhildenb/git/qemu/tests/tcg/s390x/vlgv.c:8:5: error: impossible
constraint in 'asm'
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-02-27 13:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 11:14 [Qemu-devel] [PATCH RFC 0/2] tests/tcg: Vector instruction tests for target/s390x David Hildenbrand
2019-02-27 11:14 ` [Qemu-devel] [PATCH RFC 1/2] tests/tcg: Allow targets to set the optimization level David Hildenbrand
2019-02-27 11:46 ` Alex Bennée
2019-02-27 11:58 ` David Hildenbrand
2019-02-27 12:42 ` David Hildenbrand [this message]
2019-02-27 13:44 ` David Hildenbrand
2019-02-28 0:26 ` Richard Henderson
2019-02-27 11:14 ` [Qemu-devel] [PATCH RFC 2/2] tests/tcg: target/s390: Add test for VECTOR LOAD GR FROM VR ELEMENT David Hildenbrand
2019-02-27 11:19 ` David Hildenbrand
2019-02-27 19:37 ` David Hildenbrand
2019-02-27 20:19 ` Alex Bennée
2019-02-27 20:20 ` David Hildenbrand
2019-02-27 21:40 ` Alex Bennée
2019-02-28 0:24 ` Richard Henderson
2019-02-28 7:11 ` David Hildenbrand
2019-02-28 0:17 ` Richard Henderson
2019-02-28 7:14 ` David Hildenbrand
2019-02-28 17:39 ` Richard Henderson
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=467f1311-0534-232d-b85d-2d6e0fd47661@redhat.com \
--to=david@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
/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).