[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings
From: |
Cornelia Huck |
Subject: |
Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings |
Date: |
Tue, 27 Oct 2020 12:38:46 +0100 |
On Tue, 27 Oct 2020 12:26:21 +0100
Thomas Huth <thuth@redhat.com> wrote:
> On 26/10/2020 16.12, Paolo Bonzini wrote:
> > On 26/10/20 16:03, Daniele Buono wrote:
> >> Hi Paolo,
> >> I reorganized UASStatus to put uas_iu at the end and it works fine.
> >> Unfortunately, this uncovered another part of the code with a similar
> >> issue (variable sized type not at the end of the struct), here:
> >>
> >> In file included from ../qemu-cfi-v3/target/s390x/diag.c:21:
> >> ../qemu-cfi-v3/hw/s390x/ipl.h:161:23: error: field 'iplb' with variable
> >> sized type 'IplParameterBlock' (aka 'union IplParameterBlock') not at
> >> the end of a struct or class is a GNU extension
> >> [-Werror,-Wgnu-variable-sized-type-not-at-end]
> >> IplParameterBlock iplb;
> >> ^
> >> ../qemu-cfi-v3/hw/s390x/ipl.h:162:23: error: field 'iplb_pv' with
> >> variable sized type 'IplParameterBlock' (aka 'union IplParameterBlock')
> >> not at the end of a struct or class is a GNU extension
> >> [-Werror,-Wgnu-variable-sized-type-not-at-end]
> >> IplParameterBlock iplb_pv;
> >>
> >> My understanding is that each of these IplParameterBlock may contain
> >> either a IPLBlockPV or a IplBlockFcp, which both end with a variable
> >> sized field (an array).
> >>
> >> Adding maintainers of s390x to see if they have a suggested solution to
> >> avoid disabling the warning.
> >
> > This one seems okay because the union constrains the size to 4K. If
> > "[0]" is enough to shut up the compiler, I'd say do that.
>
> The "IplBlockFcp fcp" part seems to be completely unused, so I think you
> could even remove that IplBlockFcp struct. For IPLBlockPV I agree with
> Paolo, it's likely easiest to use [0] for that struct.
The fcp block had probably been added for completeness' sake, but we do
not support list-directed IPL anyway. Not sure if we actually want it,
as we use a different mechanism for IPLing from SCSI devices. So yes,
maybe we should just drop it.
- [PATCH v2 1/6] fuzz: Make fork_fuzz.ld compatible with LLVM's LLD, (continued)
- [PATCH v2 1/6] fuzz: Make fork_fuzz.ld compatible with LLVM's LLD, Daniele Buono, 2020/10/23
- [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Daniele Buono, 2020/10/23
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Thomas Huth, 2020/10/24
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Paolo Bonzini, 2020/10/26
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Daniele Buono, 2020/10/26
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Paolo Bonzini, 2020/10/26
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Daniele Buono, 2020/10/26
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Peter Maydell, 2020/10/26
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Thomas Huth, 2020/10/27
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings,
Cornelia Huck <=
- Re: [PATCH v2 2/6] configure: avoid new clang 11+ warnings, Daniele Buono, 2020/10/27
[PATCH v2 3/6] configure: add option to enable LTO, Daniele Buono, 2020/10/23
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Paolo Bonzini, 2020/10/26
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Daniel P . Berrangé, 2020/10/26
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Daniele Buono, 2020/10/27
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Daniel P . Berrangé, 2020/10/27
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Daniele Buono, 2020/10/27
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Paolo Bonzini, 2020/10/28
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Daniele Buono, 2020/10/28
- Re: [PATCH v2 3/6] configure: add option to enable LTO, Paolo Bonzini, 2020/10/29