public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/102462] vectorization breaks diagnostic for array out of bound detect. Date: Wed, 13 Oct 2021 02:30:06 +0000 [thread overview] Message-ID: <bug-102462-4-lNe5lzhm56@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102462-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102462 --- Comment #9 from Hongtao.liu <crazylht at gmail dot com> --- case 1: All accesses are out of bound, and after vectorization, there are some warnings missing.(Because there only 1 access after vectorization, 2 accesses w/o vectorization, and diagnostic is based on access). from c-c++-common/Wstringop-overflow-2.c struct A1 a1__ = { 0 }; void ga1__ (void) { a1__.a[0] = 0; a1__.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a1__.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" } struct A1 a = { 1 }; a.a[0] = 0; // After vectorization, below codes are optimized to // vector(2) char = { 1, 2}, there's only 1 access remained, so add xfail // to a.a[2] = 2, refer to pr102462. a.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" "" { xfail { i?86-*-* x86_64-*-* } } } sink (&a); } struct A1 a1_0 = { 0, { } }; void ga1_0_ (void) { a1_0.a[0] = 0; a1_0.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a1_0.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" } struct A1 a = { 1, { } }; a.a[0] = 0; a.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" "" { xfail { i?86-*-* x86_64-*-* } } } sink (&a); } struct A1i a1i__ = { 0 }; void ga1i__ (void) { a1i__.a[0] = 0; a1i__.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a1i__.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" } struct A1i a = { 0 }; a.a[0] = 0; a.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" "" { xfail { i?86-*-* x86_64-*-* } } } sink (&a); } struct A1 a1i_0 = { 0, { } }; void ga1i_0_ (void) { a1i_0.a[0] = 0; a1i_0.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a1i_0.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" } struct A1 a = { 0, { } }; a.a[0] = 0; a.a[1] = 1; // { dg-warning "\\\[-Wstringop-overflow" } a.a[2] = 2; // { dg-warning "\\\[-Wstringop-overflow" "" { xfail { i?86-*-* x86_64-*-* } } } sink (&a); }
next prev parent reply other threads:[~2021-10-13 2:30 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-23 3:07 [Bug tree-optimization/102462] New: vectorizer " crazylht at gmail dot com 2021-09-23 3:52 ` [Bug tree-optimization/102462] vectorization " crazylht at gmail dot com 2021-09-23 6:46 ` rguenth at gcc dot gnu.org 2021-09-23 7:01 ` crazylht at gmail dot com 2021-09-23 7:03 ` crazylht at gmail dot com 2021-09-23 7:05 ` crazylht at gmail dot com 2021-09-23 7:38 ` crazylht at gmail dot com 2021-09-23 14:44 ` msebor at gcc dot gnu.org 2021-09-26 2:19 ` crazylht at gmail dot com 2021-10-13 2:30 ` crazylht at gmail dot com [this message] 2021-10-20 2:13 ` cvs-commit 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-102462-4-lNe5lzhm56@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: linkBe 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).