https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107581
--- Comment #3 from Marc Poulhiès <dkm at gcc dot gnu.org> --- (In reply to Ian Lance Taylor from comment #1) > This crash appears to be fairly deep in the middle-end. Nothing has changed > recently in the Go frontend. Has this crash just started appearing, or is > this the first time you are trying this? If it is a relatively new crash > then I think it must be related to some middle-end change. Thanks. This is a first try. I was trying 12.2.0 (ICE) then checked with trunk to see if it was still crashing. (In reply to Richard Biener from comment #2) > I assume that reproducing with trunk is with checking enabled? It would be > nice if you can do a debugging session on the crashing go1 invocation and > inspect the GIMPLE that's being expanded. From the backtrace it looks like > it's some I don't think the build has any checking enabled but I have to check (that's from a crosstool-ng build, so I doubt they are enabling checks). I'll do a debug build and add the more detailed log here. Thanks
