https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41898
--- Comment #5 from Richard Biener ---
Possibly related (implementation-wise) are ideas to handle array element
contents field-sensitive but not elements, thus have for
T p[10];
fields for members of 'T' but re-use the appropriate member for ea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41898
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41898
Martin Sebor changed:
What|Removed |Added
Last reconfirmed|2009-11-01 20:59:25 |2020-2-28
CC|
--- Comment #2 from rguenth at gcc dot gnu dot org 2009-11-01 21:00 ---
It works with
int * __restrict__ a;
int * __restrict__ b;
extern void link_error (void);
int main()
{
a[0] = 0;
b[0] = 1;
if (a[0] != 0)
link_error ();
return 0;
}
--
rguenth at gcc dot gnu dot org
--- Comment #1 from rguenth at gcc dot gnu dot org 2009-11-01 20:59 ---
Without __restrict__ we don't optimize the call to link_error either. Because
the stores may alias - they are only redundant because of the identical
RHS. See PR23094 for that missed optimization.
But restrict ind
