qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Brian Cain <brian.cain@oss.qualcomm.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/tcg: Suppress compiler false-positive warning on sha1.c
Date: Wed, 5 Mar 2025 16:52:22 +0000	[thread overview]
Message-ID: <CAFEAcA-ya3qjG4P500p7=PwWdiX4yRWKxAv1Q_SKeJSgiqXZpw@mail.gmail.com> (raw)
In-Reply-To: <2de21adf-204b-4417-aa2b-2d16d22148f8@oss.qualcomm.com>

On Wed, 5 Mar 2025 at 14:56, Brian Cain <brian.cain@oss.qualcomm.com> wrote:
> I was going to volunteer to update the toolchain used for hexagon to
> address this.  But unfortunately this warning is still not supported in
> clang 21.
>
> https://github.com/llvm/llvm-project/issues/72455 sounds like it's not
> very likely to arrive any time soon.
>
>
> So "-Wno-unknown-warning-option" does indeed seem like a good workaround.

I think the main problem with clang is that it doesn't default to
"don't complain about unknown warning options", whereas gcc does:

e104462:noble:qemu$ gcc -Wno-bang -o /tmp/hello /tmp/hello.c
e104462:noble:qemu$ clang -Wno-bang -o /tmp/hello /tmp/hello.c
warning: unknown warning option '-Wno-bang' [-Wunknown-warning-option]
1 warning generated.

-- PMM


  reply	other threads:[~2025-03-05 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 14:13 [PATCH] tests/tcg: Suppress compiler false-positive warning on sha1.c Peter Maydell
2025-02-27 16:35 ` Richard Henderson
2025-02-27 22:23 ` Alex Bennée
2025-03-04 11:56 ` Alex Bennée
2025-03-04 12:51   ` Peter Maydell
2025-03-04 13:44     ` Alex Bennée
2025-03-04 13:53       ` Peter Maydell
2025-03-04 14:29         ` Alex Bennée
2025-03-04 14:36           ` Peter Maydell
2025-03-04 15:58             ` Alex Bennée
2025-03-05 14:56     ` Brian Cain
2025-03-05 16:52       ` Peter Maydell [this message]
2025-03-05 16:56       ` Alex Bennée

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='CAFEAcA-ya3qjG4P500p7=PwWdiX4yRWKxAv1Q_SKeJSgiqXZpw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=brian.cain@oss.qualcomm.com \
    --cc=qemu-arm@nongnu.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).