From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Alexander Bulekov <alxndr@bu.edu>
Cc: Miroslav Rezanina <mrezanin@redhat.com>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/2] Fix net.c warning on GCC 11
Date: Thu, 14 Jan 2021 15:35:36 +0100 [thread overview]
Message-ID: <9a611ea5-697c-26ea-875e-0f1b2cb0bff3@redhat.com> (raw)
In-Reply-To: <20210114141920.qjsnlt3cmkauggtw@mozz.bu.edu>
On 1/14/21 3:19 PM, Alexander Bulekov wrote:
> On 210114 1415, Philippe Mathieu-Daudé wrote:
>> +Jason +Dmitry
>>
>> On 1/14/21 8:07 AM, Miroslav Rezanina wrote:
>>> When building qemu with GCC 11, compiling eth.c file produce following warning:
>>>
>>> warning: array subscript 'struct ip6_ext_hdr_routing[0]' is partly outside array bounds of 'struct ip6_ext_hdr[1]' [-Warray-bounds]
>>>
>>> This is caused by retyping from ip6_ext_hdr to ip6_ext_hdr_routing that has more
>>> attributes.
>>>
>>> As this usage is expected, suppress the warning temporarily through the function
>>> using this retyping.
>>
>> This is not expected, this is a bug...
>>
>
> Seems related: https://bugs.launchpad.net/qemu/+bug/1879531
Yes!
next prev parent reply other threads:[~2021-01-14 14:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 7:07 [PATCH v3 0/2] Fixing several GCC 11 warnings Miroslav Rezanina
2021-01-14 7:07 ` [PATCH v3 1/2] Fix net.c warning on GCC 11 Miroslav Rezanina
2021-01-14 13:15 ` Philippe Mathieu-Daudé
2021-01-14 14:19 ` Alexander Bulekov
2021-01-14 14:35 ` Philippe Mathieu-Daudé [this message]
2021-01-14 14:38 ` Miroslav Rezanina
2021-01-14 14:42 ` Alexander Bulekov
2021-01-14 15:09 ` Philippe Mathieu-Daudé
2021-01-14 14:36 ` Miroslav Rezanina
2021-01-14 7:07 ` [PATCH v3 2/2] s390x: Use strpadcpy for copying vm name Miroslav Rezanina
2021-01-14 8:32 ` Thomas Huth
2021-01-14 10:16 ` Cornelia Huck
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=9a611ea5-697c-26ea-875e-0f1b2cb0bff3@redhat.com \
--to=philmd@redhat.com \
--cc=alxndr@bu.edu \
--cc=dmitry.fleytman@gmail.com \
--cc=jasowang@redhat.com \
--cc=mrezanin@redhat.com \
--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).