public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96963] [10/11 Regression] -Wstringop-overflow false positive on -O3 or -O2 -ftree-vectorize when assigning consecutive char struct members
Date: Thu, 04 Mar 2021 00:05:41 +0000 [thread overview]
Message-ID: <bug-96963-4-W62ktchUOZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96963-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96963
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:8d57bdadd2d9c2e5c95515ca7a583d7b407b55c4
commit r11-7497-g8d57bdadd2d9c2e5c95515ca7a583d7b407b55c4
Author: Martin Sebor <msebor@redhat.com>
Date: Wed Mar 3 16:56:45 2021 -0700
Correct a workaround for vectorized stores.
Resolves:
PR middle-end/96963 - -Wstringop-overflow false positive with
-ftree-vectorize when assigning consecutive char struct members
PR middle-end/94655 - -Wstringop-overflow on implicit string assignment
with vectorized char store
gcc/ChangeLog:
PR middle-end/96963
PR middle-end/94655
* builtins.c (handle_array_ref): New helper.
(handle_mem_ref): New helper.
(compute_objsize_r): Factor out ARRAY_REF and MEM_REF handling
into new helper functions. Correct a workaround for vectorized
assignments.
gcc/testsuite/ChangeLog:
PR middle-end/96963
PR middle-end/94655
* gcc.dg/Wstringop-overflow-47.c: Xfail tests.
* gcc.dg/Wstringop-overflow-65.c: New test.
* gcc.dg/Warray-bounds-69.c: Same.
next prev parent reply other threads:[~2021-03-04 0:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 20:46 [Bug tree-optimization/96963] New: " gcc_bugzilla at venus dot thegavinli.com
2020-09-07 23:15 ` [Bug tree-optimization/96963] " msebor at gcc dot gnu.org
2020-09-08 6:45 ` rguenth at gcc dot gnu.org
2020-09-08 8:18 ` gcc_bugzilla at venus dot thegavinli.com
2020-12-06 21:55 ` msebor at gcc dot gnu.org
2020-12-07 10:40 ` redi at gcc dot gnu.org
2020-12-07 10:43 ` [Bug tree-optimization/96963] [10/11 Regression] " redi at gcc dot gnu.org
2020-12-07 12:03 ` jakub at gcc dot gnu.org
2020-12-07 21:41 ` egallager at gcc dot gnu.org
2021-01-14 9:19 ` rguenth at gcc dot gnu.org
2021-01-21 21:21 ` msebor at gcc dot gnu.org
2021-01-21 23:49 ` msebor at gcc dot gnu.org
2021-03-04 0:05 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-08 12:02 ` [Bug tree-optimization/96963] [10 " rguenth at gcc dot gnu.org
2021-07-21 16:24 ` pinskia at gcc dot gnu.org
2021-09-08 23:37 ` pinskia at gcc dot gnu.org
2022-03-17 19:45 ` msebor at gcc dot gnu.org
2022-06-28 10:41 ` jakub at gcc dot gnu.org
2023-02-04 4:42 ` pokechu022+gccbugzilla at gmail dot com
2023-07-07 9:04 ` rguenth at gcc dot gnu.org
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=bug-96963-4-W62ktchUOZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).