[Bug tree-optimization/94416] passing a restricted pointer to a function can be assumed not to modify an accessed object

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94416

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
             Blocks|                            |49774
         Resolution|---                         |DUPLICATE

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think there's a duplicate somewhere.  We currently cannot encode "restrict"
into the "accesses" implied by a call.

Note there's slight complication when g (b) eventually recurses into 'f'
passing this 'b' as 'a'.  Recursion makes the interpretation of the
lexically defined restrict concept a bit weird.

So I think this bug can be closed as duplicate of the "restrict and calls"
bug.

*** This bug has been marked as a duplicate of bug 89479 ***


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49774
[Bug 49774] [meta-bug] restrict qualification aliasing issues