https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #16 from boger at us dot ibm.com --- After further investigation I found the original testcase failures started happening with an earlier commit, which I have verified as 247497. That commit caused 7 new libgo testcase failures, but at the time, it didn't cause the error log to grow excessively so went unnoticed. When the large gofrontend change went in, then the same failures occurred but it was at that point when the information written to the error log grew to an excessive size. Probably due to the random nature of the original bug. One additional note, when debugging a few other failures, I found that when calling runtime.typedmemmove from reflect.typedmemmove, the second argument is not being initialized, which results in a SEGV for some tests (reflect, archive/tar, mime/multipart). It might be easier to compile the file containing reflect.typedmemmove and dump out the intermediate output?
