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 middle-end/67442] [5/6 Regression] GCC 5.2.0 on x86_64 creates invalid address on specific array index calculation through pointer Date: Thu, 03 Sep 2015 08:24:00 -0000 [thread overview] Message-ID: <bug-67442-4-LGSsLTGwr9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67442-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67442 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Version|unknown |5.2.0 Keywords| |wrong-code Last reconfirmed| |2015-09-03 Component|target |middle-end Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Summary|GCC 5.2.0 on x86_64 creates |[5/6 Regression] GCC 5.2.0 |invalid address on specific |on x86_64 creates invalid |array index calculation |address on specific array |through pointer |index calculation through | |pointer Target Milestone|--- |5.3 Known to fail| |5.2.0, 6.0 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed on x86_64 and the 5 branch with -O1 even: main: .LFB0: .cfi_startproc movabsq $foo+4294967408, %rax movswl (%rax), %eax ret .original has: short int value = *(bar + (sizetype) (((long unsigned int) i * (long unsigned int) j) * 4294967292 + 16)); works correctly with -fstrict-overflow (or -O2). Some bug in folding somewhere. 4.8 and 4.9 have short int value = *(bar + (sizetype) (((long unsigned int) i * (long unsigned int) j) * 18446744073709551612 + 16));
next prev parent reply other threads:[~2015-09-03 8:24 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-03 7:00 [Bug c/67442] New: " jussi.judin at ericsson dot com 2015-09-03 8:24 ` rguenth at gcc dot gnu.org [this message] 2015-09-03 8:27 ` [Bug middle-end/67442] [5/6 Regression] " mpolacek at gcc dot gnu.org 2015-09-03 8:44 ` rguenth at gcc dot gnu.org 2015-09-03 8:59 ` rguenth at gcc dot gnu.org 2015-09-03 9:02 ` rguenth at gcc dot gnu.org 2015-09-03 9:09 ` rguenth at gcc dot gnu.org 2015-09-03 9:11 ` rguenth at gcc dot gnu.org 2015-09-03 9:28 ` rguenth at gcc dot gnu.org 2015-09-03 10:04 ` rguenth at gcc dot gnu.org 2015-09-15 14:21 ` rguenth at gcc dot gnu.org 2015-09-16 7:25 ` rguenth at gcc dot gnu.org 2015-09-16 7:26 ` [Bug middle-end/67442] [5 " rguenth at gcc dot gnu.org 2015-09-28 10:46 ` rguenth at gcc dot gnu.org 2015-09-28 10:46 ` 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-67442-4-LGSsLTGwr9@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).