From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Fam Zheng <fam@euphon.net>, qemu-devel@nongnu.org
Subject: Re: [PATCH] .travis.yml: Build acceptance tests with -O2 compiler optimization
Date: Sun, 21 Jun 2020 20:05:25 +0200 [thread overview]
Message-ID: <be1726dd-c84e-b874-e2b2-7fe2cee92b8a@amsat.org> (raw)
In-Reply-To: <874kr4bn71.fsf@linaro.org>
On 6/21/20 2:47 PM, Alex Bennée wrote:
>
> Philippe Mathieu-Daudé <f4bug@amsat.org> writes:
>
>> On 6/21/20 1:29 AM, Philippe Mathieu-Daudé wrote:
>>> As we just want the tests to succeed, build them with compiler
>>> optimizations enabled to run the tests faster.
>>
>> Maybe it is a good opportunity to test -O3 instead...
>> Since this configuration is not covered.
>
> Don't know if -O3 is worth it - even Gentoo developers warn against
> cranking it up too much.
>
> In fact I'm surprised we don't build -O2 by default.
Do you mean in Travis or directly in ./configure?
>
>>
>>>
>>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>> ---
>>> .travis.yml | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/.travis.yml b/.travis.yml
>>> index 74158f741b..61b247db9f 100644
>>> --- a/.travis.yml
>>> +++ b/.travis.yml
>>> @@ -293,7 +293,7 @@ jobs:
>>> - name: "GCC check-acceptance"
>>> dist: bionic
>>> env:
>>> - - CONFIG="--enable-tools --target-list=aarch64-softmmu,alpha-softmmu,arm-softmmu,m68k-softmmu,microblaze-softmmu,mips-softmmu,mips64el-softmmu,nios2-softmmu,or1k-softmmu,ppc-softmmu,ppc64-softmmu,s390x-softmmu,sh4-softmmu,sparc-softmmu,x86_64-softmmu,xtensa-softmmu"
>>> + - CONFIG="--extra-cflags=-O2 --enable-tools --target-list=aarch64-softmmu,alpha-softmmu,arm-softmmu,m68k-softmmu,microblaze-softmmu,mips-softmmu,mips64el-softmmu,nios2-softmmu,or1k-softmmu,ppc-softmmu,ppc64-softmmu,s390x-softmmu,sh4-softmmu,sparc-softmmu,x86_64-softmmu,xtensa-softmmu"
>>> - TEST_CMD="make check-acceptance"
>>> - CACHE_NAME="${TRAVIS_BRANCH}-linux-gcc-acceptance"
>>> after_script:
>>>
>
>
next prev parent reply other threads:[~2020-06-21 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 23:29 [PATCH] .travis.yml: Build acceptance tests with -O2 compiler optimization Philippe Mathieu-Daudé
2020-06-21 12:08 ` Philippe Mathieu-Daudé
2020-06-21 12:47 ` Alex Bennée
2020-06-21 18:05 ` Philippe Mathieu-Daudé [this message]
2020-06-22 8:21 ` Philippe Mathieu-Daudé
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=be1726dd-c84e-b874-e2b2-7fe2cee92b8a@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--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).