From: Thomas Huth <thuth@redhat.com>
To: Gavin Shan <gshan@redhat.com>, qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org, laurent@vivier.eu,
qemu-arm@nongnu.org, shan.gavin@gmail.com, pbonzini@redhat.com,
philmd@redhat.com
Subject: Re: [PATCH] configure: Improve alias attribute check
Date: Sat, 20 Mar 2021 05:48:32 +0100 [thread overview]
Message-ID: <584e6cec-dd1d-7aa5-5f67-43bfcd9ae66a@redhat.com> (raw)
In-Reply-To: <20210320042753.69297-1-gshan@redhat.com>
On 20/03/2021 05.27, Gavin Shan wrote:
> It's still possible that the wrong value is returned from the alias
> of variable even if the program can be compiled without issue. This
> improves the check by executing the binary to check the result.
>
> If alias attribute can't be working properly, the @target_page in
> exec-vary.c will always return zeroes when we have the following gcc
> version.
>
> # gcc --version
> gcc (GCC) 11.0.0 20210210 (Red Hat 11.0.0-0)
>
> This abstracts the code from exec-vary.c and use it as indicator to
> enable gcc alias attribute or not.
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> ---
> configure | 34 ++++++++++++++++++++++++++++++----
> 1 file changed, 30 insertions(+), 4 deletions(-)
>
> diff --git a/configure b/configure
> index f7d022a5db..8321f380d5 100755
> --- a/configure
> +++ b/configure
> @@ -75,6 +75,7 @@ fi
>
> TMPB="qemu-conf"
> TMPC="${TMPDIR1}/${TMPB}.c"
> +TMPC_B="${TMPDIR1}/${TMPB}_b.c"
> TMPO="${TMPDIR1}/${TMPB}.o"
> TMPCXX="${TMPDIR1}/${TMPB}.cxx"
> TMPE="${TMPDIR1}/${TMPB}.exe"
> @@ -4878,13 +4879,38 @@ fi
>
> attralias=no
> cat > $TMPC << EOF
> -int x = 1;
> +static int x;
> extern const int y __attribute__((alias("x")));
> -int main(void) { return 0; }
> +extern int read_y(void);
> +void write_x(int val);
> +
> +void write_x(int val)
> +{
> + x = val;
> +}
> +
> +int main(void)
> +{
> + return read_y();
> +}
> EOF
> -if compile_prog "" "" ; then
> - attralias=yes
> +cat > $TMPC_B << EOF
> +extern const int y;
> +extern void write_x(int val);
> +int read_y(void);
> +
> +int read_y(void)
> +{
> + write_x(1);
> + return y;
> +}
> +EOF
> +
> +TMPC+=" ${TMPC_B}"
> +if compile_prog "" "" && ! $TMPE; then
What about cross-compiling? Running an executable won't work if QEMU gets
cross-compiled...
Thomas
next prev parent reply other threads:[~2021-03-20 4:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 4:27 [PATCH] configure: Improve alias attribute check Gavin Shan
2021-03-20 4:48 ` Thomas Huth [this message]
2021-03-20 23:32 ` Gavin Shan
2021-03-20 17:52 ` Paolo Bonzini
2021-03-20 22:33 ` Richard Henderson
2021-03-20 23:36 ` Gavin Shan
2021-03-21 15:49 ` Richard Henderson
2021-03-21 16:50 ` Paolo Bonzini
2021-03-21 17:34 ` Richard Henderson
2021-03-21 17:43 ` Paolo Bonzini
2021-03-21 17:46 ` Paolo Bonzini
2021-03-21 18:23 ` Richard Henderson
2021-03-22 10:54 ` Gavin Shan
2021-03-22 20:59 ` Richard Henderson
2021-03-23 3:13 ` Gavin Shan
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=584e6cec-dd1d-7aa5-5f67-43bfcd9ae66a@redhat.com \
--to=thuth@redhat.com \
--cc=gshan@redhat.com \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shan.gavin@gmail.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).