https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89123
--- Comment #5 from rdapp at linux dot ibm.com ---
I performed a bisect using const-1.go as check and got the following likely
culprit:
b0751b120f1b83d8e48a7c2cac831aabbb0bc048 is the first bad commit
commit b0751b120f1b83d8e48a7c2cac831aabbb0bc048
Author: ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Mon Sep 24 21:46:21 2018 +0000
libgo: update to Go 1.11
Reviewed-on: https://go-review.googlesource.com/136435
(rev. 264546)
Dominik Vogt is no longer with IBM, so I'm going to look into it. I have no
experience with go yet, though. Might this simply be a case of an oversight
regarding big endian? Do we have another big-endian backend where go works?
