cmd/compile: inline static init cause compile time error

[cuonglm]

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

$ go version
go version go1.20 linux/amd64

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

What did you do?

package main

var x = f(-1)
var y = f(64)

func f(x int) int {
	return 1 << x
}

func main() {
	println(x, y)
}

What did you expect to see?

Runtime error.

What did you see instead?

Compile time error.

[cuonglm]

The fix for #58293 only deal with the integer overflow case.

[cuonglm]

This needs to be backport, too cc @randall77 @mdempsky @dr2chase

There're a plenty of issue with inline static init happens, and although I think https://go-review.googlesource.com/c/go/+/466277 should fix them, maybe a safer way to backport is disable inline static init for go1.20, then re-enable by default during go1.21 cycle.

[gopherbot]

Change https://go.dev/cl/466277 mentions this issue: cmd/compile: rename EvalConst to EvalExpr

[randall77]

I agree, probably the safest thing to do for 1.20 is just disable inline static init. We can fix for 1.21 properly.

[mdempsky]

Disabling the optimization for 1.20 seems right to me too, unfortunately.

[cuonglm]

@gopherbot please backport this issue to 1.20

[gopherbot]

Backport issue(s) opened: #58444 (for 1.20).

Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases.

[gopherbot]

Change https://go.dev/cl/467016 mentions this issue: cmd/compile: reenable inline static init