https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
--- Comment #7 from Richard Biener ---
Oh, and with LTO you _should_ see all pointed-to objects and thus restrict
should be no longer necessary... (well, in theory)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
--- Comment #6 from rguenther at suse dot de ---
On Tue, 5 Apr 2016, vries at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
>
> --- Comment #5 from vries at gcc dot gnu.org ---
> Created attachment 38189
> --> ht
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
--- Comment #5 from vries at gcc dot gnu.org ---
Created attachment 38189
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38189&action=edit
patch to recompute restrict info after ipa-pta
(In reply to Richard Biener from comment #4)
> One pos
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
--- Comment #4 from Richard Biener ---
One possibility would be to re-run non-IPA PTA just to compute restrict info,
that is, instead of bailing out when cfun->gimple_df->ipa_pta just not update
SSA pointer-info but still call compute_dependence_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
--- Comment #3 from vries at gcc dot gnu.org ---
(In reply to vries from comment #2)
> This is in particular problematic for fortran and fopenmp/fopenacc, where
> the non-aliasing of parameters arrays in fortran is implemented by annotated
> those
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
--- Comment #2 from vries at gcc dot gnu.org ---
This is in particular problematic for fortran and fopenmp/fopenacc, where the
non-aliasing of parameters arrays in fortran is implemented by annotated those
parameters with restrict in the fortran f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68787
vries at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
