cmd/compile: fuzzing triggers various crashes or internal compiler errors on tip #49019
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsFix
The path to resolution is known, but the work has not been done.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, tip.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Fuzz cmd/compile using dvyukov/go-fuzz. (This is partially a follow-up to #39634, but there I was just fuzzing the type checker, whereas this was fuzzing the full cmd/compile).
Most of the fuzzing happened on an earlier commit, but roughly half of the original crashers that were initially found no longer reproduce on tip, or seem to be tracked elsewhere (e.g., #47631 (comment)).
What did you see?
Here are 4 crashers that still reproduce on latest tip with
go tool compile
:Crash 1: goroutine stack exceeds 1000000000-byte limit
In
types2.(*unifier).nifyEq
(vianifyEq -> nify -> nifyEq -> nify -> ...
)Crash 2: internal compiler error: label missing tag
In
escape.(*escape).stmt
:Crash 3: internal compiler error: bvset: index 6 is out of bounds with length 6
In
bitvec.BitVec.Set
(viatypebits.Set
andliveness.WriteFuncMap
):Crash 4: internal compiler error: bad type
In
types.typePos
(viatypes.CalcSize
):(FYI @mdempsky -- this is a belated follow-up from our conversation from a while ago).
The text was updated successfully, but these errors were encountered: