From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Brian Cain <brian.cain@oss.qualcomm.com>
Subject: Re: [PATCH] tests/tcg: Suppress compiler false-positive warning on sha1.c
Date: Tue, 04 Mar 2025 13:44:45 +0000 [thread overview]
Message-ID: <87ikoo6hbm.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAFEAcA9VDtWKoQ09dOt+ZxJ2MhdRTFY_X1ON58pEjYTM_NtZ-A@mail.gmail.com> (Peter Maydell's message of "Tue, 4 Mar 2025 12:51:34 +0000")
Peter Maydell <peter.maydell@linaro.org> writes:
> On Tue, 4 Mar 2025 at 11:56, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> Peter Maydell <peter.maydell@linaro.org> writes:
>> > +# GCC versions 12/13/14/15 at least incorrectly complain about
>> > +# "'SHA1Transform' reading 64 bytes from a region of size 0"; see the gcc bug
>> > +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106709
>> > +# Since this is just a standard piece of library code we've borrowed for a
>> > +# TCG test case, suppress the warning rather than trying to modify the
>> > +# code to work around the compiler.
>> > +sha1: CFLAGS+=-Wno-stringop-overread
>> > +
>>
>> Sadly this breaks the hexagon compiler:
>>
>> error: unknown warning option '-Wno-stringop-overread' [-Werror,-Wunknown-warning-option]
>> Traceback (most recent call last):
>> File "/home/alex/lsrc/qemu.git/tests/docker/docker.py", line 683, in <module>
>> sys.exit(main())
>> ^^^^^^
>> File "/home/alex/lsrc/qemu.git/tests/docker/docker.py", line 679, in main
>> return args.cmdobj.run(args, argv)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> File "/home/alex/lsrc/qemu.git/tests/docker/docker.py", line 657, in run
>> return Docker().run(cmd, False, quiet=args.quiet,
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> File "/home/alex/lsrc/qemu.git/tests/docker/docker.py", line 370, in run
>> ret = self._do_check(["run", "--rm", "--label",
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> File "/home/alex/lsrc/qemu.git/tests/docker/docker.py", line 247, in _do_check
>> return subprocess.check_call(self._command + cmd, **kwargs)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
>> raise CalledProcessError(retcode, cmd)
>> subprocess.CalledProcessError: Command '['podman', 'run', '--rm', '--label', 'com.qemu.instance.uuid=5bbb7b6ed2ea4377b9b6d646859ec4ea', '--userns=keep-id', '-u', '1000', '-w', '/home/alex/lsrc/qemu.git/builds/all/tests/tcg/hexagon-linux-user', '-v', '/home/alex/lsrc/qemu.git/builds/all/tests/tcg/hexagon-linux-user:/home/alex/lsrc/qemu.git/builds/all/tests/tcg/hexagon-linux-user:rw', '-v', '/home/alex/lsrc/qemu.git:/home/alex/lsrc/qemu.git:ro,z', 'qemu/debian-hexagon-cross', 'hexagon-unknown-linux-musl-clang', '-Wno-incompatible-pointer-types', '-Wno-undefined-internal', '-fno-unroll-loops', '-fno-stack-protector', '-Wall', '-Werror', '-O0', '-g', '-fno-strict-aliasing', '-Wno-stringop-overread', '-mv73', '-O2', '-static', '/home/alex/lsrc/qemu.git/tests/tcg/multiarch/sha1.c', '-o', 'sha1', '-static']' returned non-zero exit status 1.
>> filter=--filter=label=com.qemu.instance.uuid=5bbb7b6ed2ea4377b9b6d646859ec4ea
>> make[1]: *** [Makefile:122: sha1] Error 1
>> make: *** [/home/alex/lsrc/qemu.git/tests/Makefile.include:52: build-tcg-tests-hexagon-linux-user] Error 2
>>
>> Is it that new an option?
>
> I think it's new-ish (gcc 11?). On the other hand
> -Wno-unknown-warning-option is quite old, and would suppress
> this error. If we do
> CFLAGS+=-Wno-unknown-warning-option -Wno-stringop-overread
>
> does that work?
Yes, I did:
modified tests/tcg/hexagon/Makefile.target
@@ -18,7 +18,7 @@
# Hexagon doesn't support gdb, so skip the EXTRA_RUNS
EXTRA_RUNS =
-CFLAGS += -Wno-incompatible-pointer-types -Wno-undefined-internal
+CFLAGS += -Wno-incompatible-pointer-types -Wno-undefined-internal -Wno-unknown-warning-option
CFLAGS += -fno-unroll-loops -fno-stack-protector
>
> (Meson has cc.get_supported_arguments() that we can use to
> filter out -Wfoo/-Wno-foo options that the compiler doesn't
> support, but since this is built via a makefile rather than
> by meson that's not conveniently accessible.)
>
> -- PMM
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-03-04 13:44 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 [this message]
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
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=87ikoo6hbm.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=brian.cain@oss.qualcomm.com \
--cc=peter.maydell@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.