https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80914
--- Comment #12 from Steven Noonan <steven at uplinklabs dot net> --- Oh this is kind of interesting. It runs fine at '-O1 -ggdb3' $ go.gcc test -o testbin -gccgoflags '-O1 -ggdb3 -Wl,--compress-debug-sections=zlib' OK: 136 passed PASS ok github.com/twstrike/ed448 0.289s And at '-O0 -g0': $ go.gcc test -o testbin1 -gccgoflags '-O0 -g0 -Wl,--compress-debug-sections=zlib' OK: 136 passed PASS ok github.com/twstrike/ed448 0.496s But not at '-O0 -ggdb3': $ go.gcc test -o testbin -gccgoflags '-O0 -ggdb3 -Wl,--compress-debug-sections=zlib' fatal error: ranges offset out of range goroutine 1 [running, locked to thread]: fatal error: ranges offset out of range panic during panic goroutine 1 [running, locked to thread]: fatal error: ranges offset out of range stack trace unavailable exit status 4 FAIL github.com/twstrike/ed448 0.054s
