From: Olaf Hering <olaf@aepfle.de>
To: qemu-devel@nongnu.org
Subject: 8.1-rc0 testfloat fails to compile
Date: Thu, 20 Jul 2023 22:47:15 +0200 [thread overview]
Message-ID: <20230720224656.2841ff5f.olaf@aepfle.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
This is going on since a few weeks. I guess there is no check in CI to see if qemu.git#master compiles in Tumbleweed.
Since the switch to meson submodules, berkeley-testfloat-3 became mandatory. I think in the past I was able to ignore this submodule and not export it, so the following error did not show up:
[ 141s] ../subprojects/berkeley-testfloat-3/source/genCases_f64.c: In function 'f64Random':
[ 141s] ../subprojects/berkeley-testfloat-3/source/genCases_f64.c:559:1: error: control reaches end of non-void function [-Werror=return-type]
[ 141s] 559 | }
[ 141s] | ^
[ 141s] cc1: some warnings being treated as errors
Apparently this is a known issue, 3ac1f81329f attempted to ignore such errors.
Do I need to tweak the global, system-provided CFLAGS myself, or can the source be fixed to address this? Disabling this error globally will hide errors elsewhere.
Maybe there is a way to append something to tests/fp/meson.build:libtestfloat.c_args? Right now it is apparently set to tfcflags+fpcflags+CFLAGS.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-07-20 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 20:47 Olaf Hering [this message]
2023-07-21 6:54 ` 8.1-rc0 testfloat fails to compile Thomas Huth
2023-07-21 7:03 ` Olaf Hering
2023-07-21 7:18 ` Thomas Huth
2023-07-21 7:35 ` Olaf Hering
2023-07-21 7:53 ` Thomas Huth
2023-07-21 8:04 ` Olaf Hering
2023-07-22 12:49 ` Richard Henderson
2023-07-24 12:37 ` Olaf Hering
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=20230720224656.2841ff5f.olaf@aepfle.de \
--to=olaf@aepfle.de \
--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.