[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict

2020-10-06 Thread vries at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97159 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict

2020-10-05 Thread vries at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97159 --- Comment #4 from Tom de Vries --- I'm currently not running into this ICE anymore, so presumably it was fixed. I'm not sure by which commit though.

Re: [Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict

2020-09-22 Thread Jan Hubicka
Recursion is handled in normal compilation (we analyze the function and while hitting the recursive call we skip the summary). I suppose here the problem is missing LTO and offloading. With LTO lto summaries (that include types) are streamed out while they are turned into non-lto summaries at ltr

[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict

2020-09-22 Thread hubicka at ucw dot cz
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97159 --- Comment #3 from Jan Hubicka --- Recursion is handled in normal compilation (we analyze the function and while hitting the recursive call we skip the summary). I suppose here the problem is missing LTO and offloading. With LTO lto summaries

[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict

2020-09-22 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97159 Richard Biener changed: What|Removed |Added Target Milestone|--- |11.0 Priority|P3