qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH] configure: Add -Werror to avx2, avx512 tests
Date: Thu, 29 Jul 2021 09:54:06 +0200	[thread overview]
Message-ID: <2bf7b5c7-82ba-e5f7-0c68-173a24e3fef5@redhat.com> (raw)
In-Reply-To: <20210719200112.295316-1-richard.henderson@linaro.org>

On 19/07/21 22:01, Richard Henderson wrote:
> When using clang, we get
> 
> ERROR: configure test passed without -Werror but failed with -Werror.
>         This is probably a bug in the configure script. The failing command
>         will be at the bottom of config.log.
>         You can run configure with --disable-werror to bypass this check.
> 
> What we really want from these two tests is whether the
> entire code sequence is supported, including pragmas.
> Adding -Werror makes the test properly fail for clang.
> 
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
>   configure | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/configure b/configure
> index 63f38fa94c..cf4616f635 100755
> --- a/configure
> +++ b/configure
> @@ -3884,7 +3884,7 @@ static int bar(void *a) {
>   }
>   int main(int argc, char *argv[]) { return bar(argv[0]); }
>   EOF
> -  if compile_object "" ; then
> +  if compile_object "-Werror" ; then
>       avx2_opt="yes"
>     else
>       avx2_opt="no"
> @@ -3914,7 +3914,7 @@ int main(int argc, char *argv[])
>   	return bar(argv[0]);
>   }
>   EOF
> -  if ! compile_object "" ; then
> +  if ! compile_object "-Werror" ; then
>       avx512f_opt="no"
>     fi
>   else
> 

Queued, thanks.

Paolo



      reply	other threads:[~2021-07-29  7:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 20:01 [PATCH] configure: Add -Werror to avx2, avx512 tests Richard Henderson
2021-07-29  7:54 ` Paolo Bonzini [this message]

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=2bf7b5c7-82ba-e5f7-0c68-173a24e3fef5@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).