public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/29708] New: Alias can go funny with pointer addition Date: Sat, 04 Nov 2006 09:13:00 -0000 [thread overview] Message-ID: <bug-29708-6528@http.gcc.gnu.org/bugzilla/> (raw) With the following testcase: int a[100], b[100], d[100]; void link_error (void); int g(int i, int j) { int *c; int t; c = i?a:b; c++; d[j] = 1; c[j] = 2; if (d[j] != 1) link_error (); return 0; } ---- May-alias should figure out that c can only pointer to a or b but it gets confused as we get: j.2_11 = (unsigned int) j_7; D.1537_12 = j.2_11 * 4; D.1538_13 = (int *) D.1537_12; D.1539_14 = D.1538_13 + c_6; *D.1539_14 = 2; as may-alias only looks at the left hand side of a PLUS expression, we get the following result: D.1538_13 = &ANYTHING D.1539_14 = D.1538_13 Note 4.1 optimzed this testcase but I think that was by accident and is not actually getting it correct. If we add PTR_PLUS_EXPR we get the correct answer all the time unless someone does some real weird tricks by doing something like: size_t t = (size_t)a; int *c = (int*)(size_t)j; *(c+t) = 2; -- Summary: Alias can go funny with pointer addition Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: pinskia at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29708
next reply other threads:[~2006-11-04 9:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-04 9:13 pinskia at gcc dot gnu dot org [this message] 2006-11-04 17:21 ` [Bug tree-optimization/29708] " rguenth at gcc dot gnu dot org 2007-05-22 0:52 ` pinskia at gcc dot gnu dot org 2007-06-16 5:50 ` pinskia 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-29708-6528@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).