public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112736] [14 Regression] vectorizer is introducing out of bounds memory access Date: Mon, 11 Dec 2023 13:43:40 +0000 [thread overview] Message-ID: <bug-112736-4-LAvpM3qn6G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112736-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112736 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Runtime testcase: #include <sys/mman.h> #include <unistd.h> int a, c[3][5]; void __attribute__((noipa)) fn1 (int * __restrict b) { int e; for (a = 2; a >= 0; a--) for (e = 0; e < 4; e++) c[a][e] = b[a]; } int main() { long pgsz = sysconf (_SC_PAGESIZE); void *p = mmap (NULL, pgsz * 2, PROT_READ|PROT_WRITE, MAP_ANONYMOUS|MAP_PRIVATE, 0, 0); if (p == MAP_FAILED) return 0; mprotect (p, pgsz, PROT_NONE); fn1 (p + pgsz); return 0; }
next prev parent reply other threads:[~2023-12-11 13:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-27 22:30 [Bug tree-optimization/112736] New: " kristerw at gcc dot gnu.org 2023-11-27 22:44 ` [Bug tree-optimization/112736] [14 Regression] " pinskia at gcc dot gnu.org 2023-11-28 12:10 ` rguenth at gcc dot gnu.org 2023-12-11 13:43 ` rguenth at gcc dot gnu.org [this message] 2023-12-12 14:26 ` cvs-commit at gcc dot gnu.org 2023-12-12 14:27 ` 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-112736-4-LAvpM3qn6G@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).