[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97159 Tom de Vries changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Tom de Vries --- Marking resolved-fixed.
[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict
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
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 ltrans time. We need to do similar thing with offload. Honza
[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict
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 (that include types) are streamed out while they are turned into non-lto summaries at ltrans time. We need to do similar thing with offload. Honza
[Bug tree-optimization/97159] [11 Regression] segfault in modref_may_conflict
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97159 Richard Biener changed: What|Removed |Added Target Milestone|--- |11.0 Priority|P3 |P1 Keywords||ice-on-valid-code Summary|segfault in |[11 Regression] segfault in |modref_may_conflict |modref_may_conflict