https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81008
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81008
Martin Sebor changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81008
--- Comment #2 from Martin Sebor ---
Restrict imposes additional constraints even on accesses to objects via
non-restricted pointers. The one relevant to this report is in 6.7.3.1, p4:
-4- During each execution of B, let L be any lvalue
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81008
--- Comment #1 from Andrew Pinski ---
Are you 100% sure this is safe. IIRC there are specific rules about restrict
and it only takes about other pointers to restrict types.
