public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/41898] New: GCC ignores restrict on array Date: Sun, 01 Nov 2009 20:25:00 -0000 [thread overview] Message-ID: <bug-41898-114@http.gcc.gnu.org/bugzilla/> (raw) Adding a pointless array qualifier to the restrict-1.c test makes it not work with gcc -O2; we fail to optimize away the call to link_error. int * __restrict__ a[1]; int * __restrict__ b[1]; extern void link_error (void); int main() { a[0][0] = 1; b[0][0] = 1; if (a[0][0] != 1) link_error (); return 0; } -- Summary: GCC ignores restrict on array Product: gcc Version: 4.5.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jason at gcc dot gnu dot org BugsThisDependsOn: 6392 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41898
next reply other threads:[~2009-11-01 20:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-01 20:25 jason at gcc dot gnu dot org [this message] 2009-11-01 20:59 ` [Bug tree-optimization/41898] " rguenth at gcc dot gnu dot org 2009-11-01 21:01 ` rguenth at gcc dot gnu dot 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-41898-114@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).