https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96502
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2020-08-07
Keywords| |alias
Status|UNCONFIRMED |NEW
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
There is no reasonable way to represent this in the IL to have its effect
re-discovered via PTA. The only way to preserve some of its information is
to record the effect on data dependences like we do for restrict qualified
function arguments, thus, translate 'malloc' to base/clique pairs.
It shouldn't be difficult to do that - compute_dependence_clique would
simply need to look for is_heap_var in addition to is_restrict_var.
Note the base/clique info is by design a much weaker representation than
a full points-to set since it only tracks references that can exactly
access a single object (well, we could form groups but the implementation
currently does not). But it works complementary and thus does not weaken
points-to info if it is there.
