From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [PATCH v1 6/6] tests/i386/test-i386: try and correct constrain 16 bit call (WIP)
Date: Tue, 30 Mar 2021 14:18:55 -0700 [thread overview]
Message-ID: <b185e4cf-4db0-0a71-1a16-024aac9e9e20@linaro.org> (raw)
In-Reply-To: <CAFEAcA-UL1hYanrOb5dBJWRHhfD9VVMU5ka0TOpWdysjGH7d6g@mail.gmail.com>
On 3/30/21 2:46 PM, Peter Maydell wrote:
> On Tue, 30 Mar 2021 at 21:27, Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> On 3/30/21 12:20 PM, Alex Bennée wrote:
>>> Hmm actually the fedora-i386-cross image is:
>>>
>>> gcc (GCC) 10.2.1 20201125 (Red Hat 10.2.1-9)
>>>
>>> with CROSS_CC_GUEST_CFLAGS=-m32 so I wonder what the difference is
>>> between that and:
>>>
>>> i686-linux-gnu-gcc -m32
>>>
>>> i686-linux-gnu-gcc --version
>>> i686-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
>>> Copyright (C) 2019 Free Software Foundation, Inc.
>>> This is free software; see the source for copying conditions. There is NO
>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>>
>>> They are both pretty new.
>>
>> The difference, I'm sure, is a local distro patch enabling -fpie by default.
>>
>> I'm hoping that we can just use
>>
>> --- a/tests/tcg/i386/Makefile.target
>> +++ b/tests/tcg/i386/Makefile.target
>> @@ -10,6 +10,9 @@ ALL_X86_TESTS=$(I386_SRCS:.c=)
>> SKIP_I386_TESTS=test-i386-ssse3
>> X86_64_TESTS:=$(filter test-i386-ssse3, $(ALL_X86_TESTS))
>>
>> +# test-i386 has non-pic calls into 16-bit mode
>> +test-i386: CFLAGS += -fno-pie
>> +
>> test-i386-sse-exceptions: CFLAGS += -msse4.1 -mfpmath=sse
>> run-test-i386-sse-exceptions: QEMU_OPTS += -cpu max
>> run-plugin-test-i386-sse-exceptions-%: QEMU_OPTS += -cpu max
>
> configure will set CFLAGS_NOPIE in config-host.mak, but I don't know
> if you have access to that here. (It does suggest that there are cases
> where -fno-pie isn't available, though I guess they might be non-x86.)
I think it's merely old compilers. We do have to be worried about old host
compilers here. I'm hoping that gitlab will find out if our oldest docker
build will find out one way or another.
r~
next prev parent reply other threads:[~2021-03-30 21:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 11:02 [PATCH for 6.0-rc2? v1 0/6] check-tcg for non-x86 hosts Alex Bennée
2021-03-29 11:02 ` [PATCH v1 1/6] tests/tcg: update the defaults for x86 compilers Alex Bennée
2021-03-30 15:24 ` Richard Henderson
2021-03-29 11:02 ` [PATCH v1 2/6] tests/docker: don't set DOCKER_REGISTRY on non-x86_64 Alex Bennée
2021-03-29 11:36 ` Thomas Huth
2021-03-29 14:37 ` Willian Rampazzo
2021-03-30 15:24 ` Richard Henderson
2021-03-31 12:32 ` Philippe Mathieu-Daudé
2021-03-31 14:57 ` Alex Bennée
2021-03-29 11:03 ` [PATCH v1 3/6] tests/tcg: add concept of container_hosts Alex Bennée
2021-03-29 11:03 ` [PATCH v1 4/6] tests/tcg/configure.sh: make sure we pick up x86_64 cross compilers Alex Bennée
2021-03-29 11:03 ` [PATCH v1 5/6] tests/tcg/i386: expand .data sections for system tests Alex Bennée
2021-03-29 11:39 ` Thomas Huth
2021-03-30 15:27 ` Richard Henderson
2021-03-29 11:03 ` [PATCH v1 6/6] tests/i386/test-i386: try and correct constrain 16 bit call (WIP) Alex Bennée
2021-03-30 15:58 ` Richard Henderson
2021-03-30 18:20 ` Alex Bennée
2021-03-30 20:25 ` Richard Henderson
2021-03-30 20:46 ` Peter Maydell
2021-03-30 21:18 ` Richard Henderson [this message]
2021-03-29 11:12 ` [PATCH for 6.0-rc2? v1 0/6] check-tcg for non-x86 hosts no-reply
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=b185e4cf-4db0-0a71-1a16-024aac9e9e20@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).