gccgo: no panic on nil pointer dereference on ^ operator

[ddaa2000]

What version of Go are you using (go version)?

$ gccgo -v
Using built-in specs.
COLLECT_GCC=/usr/local/gcc-12.1.0/bin/gccgo
COLLECT_LTO_WRAPPER=/usr/local/gcc-12.1.0/libexec/gcc/x86_64-pc-linux-gnu/12.1.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-12.1.0/configure --prefix=/usr/local/gcc-12.1.0 --enable-languages=c,c++,go --with-arch-32=i586
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 12.1.0 (GCC) 

Does this issue reproduce with the latest release?

Yes.

What operating system and processor architecture are you using (go env)?

go env Output

$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/root/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/root/go"
GOPRIVATE=""
GOPROXY="https://mirrors.aliyun.com/goproxy/"
GOROOT="/usr/local/go1.18.1"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go1.18.1/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="/usr/local/gcc-12.1.0/bin/gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build847055300=/tmp/go-build -gno-record-gcc-switches"

What did you do?

https://go.dev/play/p/jbdJGKWIsuL?v=gotip

What did you expect to see?

The program throws a panic.

What did you see instead?

The program finished running and print "no panic" in gccgo-6.1.0 and gccgo-12.1.0 (other versions are not tested).

[ddaa2000]

I'm not sure whether this is duplicated of #53012 so I reported this just in case.
The difference between them is that:

1. This one can be triggered in gccgo-6.1.0 and gccgo: no panic on nil pointer dereference #53012 can only be triggered in gccgo-12.1.0.
2. This one can only be triggered when the ^ operator is used, perhaps the compiler optmized the operator since its value should be a constant if no panic is thrown.
3. This one can be triggerd even with the -O0 option.

However, it also can be the same bug about the optimization failed to consider the panic situation. Maybe the best way is to check whether the fix for #53012 can fix this one.

[ianlancetaylor]

This is also a GCC middle-end bug, but not one that I am going to try to tackle. I've filed https://gcc.gnu.org/PR106163 against GCC. Since this will have to be fixed by GCC maintainers, closing this issue in favor of that one. Thanks for reporting it.