https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89123
--- Comment #6 from Ian Lance Taylor <ian at airs dot com> --- Thanks. I could have predicted that that would be the change. Unfortunately that isn't useful as that is a huge change, bringing in a large number of upstream changes from the master Go library. While anything is possible I think it's relatively unlikely to be an endianness problem. The Go code works on a range of different processors, including big-endian ones like SPARC. It seems that programs are crashing fairly early in their run, so I recommend that you build a failing program and run it under the debugger so see where it crashes. That will probably suggest something. Or I'm willing to look at it if there is guest access available on an S/390 GNU/Linux system.
