This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/65330] restrict should be considered when folding through references from global vars
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 06 Mar 2015 10:06:52 +0000
- Subject: [Bug middle-end/65330] restrict should be considered when folding through references from global vars
- Auto-submitted: auto-generated
- References: <bug-65330-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65330
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Priority|P1 |P3
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2015-03-06
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I was thinking of sth else first - make sure that points-to analysis processes
initializers of readonly globals (when they bind to the current def). In
your testcase the globals are not readonly - or did you mean to write
int * const varptr = &var;
int * const __restrict__ varptr2 = &var;
? Your testcase also misses a declaration of 'var'.