https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55212
--- Comment #208 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> --- Building with Go enabled, fails with: during RTL pass: subreg3 ../../../libgo/go/unicode/utf16/utf16.go: In function 'unicode/utf16.Encode': ../../../libgo/go/unicode/utf16/utf16.go:56:1: internal compiler error: in decompose_multiword_subregs, at lower-subreg.cc:1728 56 | func Encode(s []rune) []uint16 { | ^ libtool: compile: /srv/glaubitz/gcc/build/./gcc/gccgo -B/srv/glaubitz/gcc/build/./gcc/ -B/usr/local/sh4-unknown-linux-gnu/bin/ -B/usr/local/sh4-unknown-linux-gnu/lib/ -isystem /usr/local/sh4-unknown-linux-gnu/include -isystem /usr/local/sh4-unknown-linux-gnu/sys-include -O2 -g -I . -c -fgo-pkgpath=internal/itoa ../../../libgo/go/internal/itoa/itoa.go -o internal/itoa.o >/dev/null 2>&1 libtool: compile: /srv/glaubitz/gcc/build/./gcc/gccgo -B/srv/glaubitz/gcc/build/./gcc/ -B/usr/local/sh4-unknown-linux-gnu/bin/ -B/usr/local/sh4-unknown-linux-gnu/lib/ -isystem /usr/local/sh4-unknown-linux-gnu/include -isystem /usr/local/sh4-unknown-linux-gnu/sys-include -O2 -g -I . -c -fgo-pkgpath=sync/atomic ../../../libgo/go/sync/atomic/doc.go ../../../libgo/go/sync/atomic/unaligned.go ../../../libgo/go/sync/atomic/value.go -o sync/atomic.o >/dev/null 2>&1 libtool: compile: /srv/glaubitz/gcc/build/./gcc/gccgo -B/srv/glaubitz/gcc/build/./gcc/ -B/usr/local/sh4-unknown-linux-gnu/bin/ -B/usr/local/sh4-unknown-linux-gnu/lib/ -isystem /usr/local/sh4-unknown-linux-gnu/include -isystem /usr/local/sh4-unknown-linux-gnu/sys-include -O2 -g -I . -c -fgo-pkgpath=container/ring ../../../libgo/go/container/ring/ring.go -o container/ring.o >/dev/null 2>&1 0x1872ddb internal_error(char const*, ...) ../../gcc/diagnostic-global-context.cc:491 0x67aca7 fancy_abort(char const*, int, char const*) ../../gcc/diagnostic.cc:1772 0x173af73 decompose_multiword_subregs ../../gcc/lower-subreg.cc:1728 0x173b8bf execute ../../gcc/lower-subreg.cc:1849 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. Not sure whether this is an old bug though.