qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Thomas Huth <thuth@redhat.com>, Olaf Hering <olaf@aepfle.de>,
	qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: 8.1-rc0 testfloat fails to compile
Date: Sat, 22 Jul 2023 13:49:40 +0100	[thread overview]
Message-ID: <f2beeb1e-fc2d-9fdd-303f-d1722aeaf63d@linaro.org> (raw)
In-Reply-To: <74d1ee57-04a7-37f7-2c85-6ce49b4ded3a@redhat.com>

On 7/21/23 07:54, Thomas Huth wrote:
> On 20/07/2023 22.47, Olaf Hering wrote:
>> 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.
> 
> We only have a check for openSUSE leap ...
> Which compiler version is causing trouble for you?
> 
>> 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.
> 
> Seems like the flag got lost in commit d2dfe0b506e47e14 ... Paolo, any ideas?
> 
>> 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.
> 
> We are using a forked version of the berkeley-testfloat repository, and it's possible to 
> add patches there:
> 
>   https://gitlab.com/qemu-project/berkeley-testfloat-3
> 
> The f64Random function that you mentioned above could easily be fixed by adding a 
> "default:" case to the switch statement, I think. Are there any other additional 
> warnings/errors after fixing this?
> 
> Feel free to send a patch and CC: the people from 
> https://gitlab.com/qemu-project/berkeley-testfloat-3/-/project_members

If this is with optimization enabled, the bug should be reported to gcc bugzilla.
The compiler should easily prove the default case is unreachable.


r~


  parent reply	other threads:[~2023-07-22 12:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 20:47 8.1-rc0 testfloat fails to compile Olaf Hering
2023-07-21  6:54 ` 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 [this message]
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=f2beeb1e-fc2d-9fdd-303f-d1722aeaf63d@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=olaf@aepfle.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).