From: Martin Sebor <msebor@gmail.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: PING 2 [PATCH] avoid -Warray-bounds checks for vtable assignments (PR 98266)
Date: Sat, 6 Feb 2021 10:12:55 -0700 [thread overview]
Message-ID: <c7daac1b-a451-e5ab-3b68-19bb6e7b114f@gmail.com> (raw)
In-Reply-To: <3d36badc-429f-98d4-51fd-df6a2fe9e218@gmail.com>
Ping 2:
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563894.html
On 1/29/21 10:22 AM, Martin Sebor wrote:
> Ping:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563894.html
>
> On 1/19/21 5:56 PM, Martin Sebor wrote:
>> Similar to the problem reported for -Wstringop-overflow in pr98266
>> and already fixed, -Warray-bounds is also susceptible to false
>> positives in assignments and copies involving virtual inheritance.
>> Because the two warnings don't share code yet (hopefully in GCC 12)
>> the attached patch adds its own workaround for this problem to
>> gimple-array-bounds.cc, this one slightly more crude because of
>> the limited insight the array bounds checking has into the checked
>> expressions.
>>
>> Tested on x86_64-linux.
>>
>> Martin
>
next prev parent reply other threads:[~2021-02-06 17:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 0:56 Martin Sebor
2021-01-29 17:22 ` PING " Martin Sebor
2021-02-06 17:12 ` Martin Sebor [this message]
2021-02-08 19:59 ` Jeff Law
2021-02-08 21:56 ` Martin Sebor
2021-02-08 22:26 ` Jeff Law
2021-02-08 22:44 ` Martin Sebor
2021-02-08 23:11 ` Jeff Law
2021-02-09 17:49 ` Martin Sebor
2021-02-23 16:02 ` PING " Martin Sebor
2021-02-23 21:52 ` Jason Merrill
2021-02-23 23:07 ` Martin Sebor
2021-02-25 0:35 ` Jason Merrill
2021-03-01 23:11 ` Martin Sebor
2021-03-02 14:11 ` Jason Merrill
2021-03-03 23:20 ` Martin Sebor
2021-03-04 5:33 ` Jason Merrill
2021-03-04 17:44 ` Martin Sebor
2021-03-04 20:00 ` Jason Merrill
2021-02-25 23:47 ` Jeff Law
2021-02-26 3:56 ` Jason Merrill
2021-02-25 23:40 ` Jeff Law
2021-03-01 23:16 ` Martin Sebor
2021-02-25 23:15 ` Jeff Law
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=c7daac1b-a451-e5ab-3b68-19bb6e7b114f@gmail.com \
--to=msebor@gmail.com \
--cc=gcc-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).