Date: Sun, 15 Dec 2024 03:37:27 +0000 From: bugzilla-noreply@freebsd.org To: go@FreeBSD.org Subject: [Bug 283314] lang/go building go app immediately fails at compile "unexpected return pc for cmd/compile/internal/ssa.Compile" Message-ID: <bug-283314-42334-HufETADT15@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283314-42334@https.bugs.freebsd.org/bugzilla/> References: <bug-283314-42334@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283314 --- Comment #1 from Mike Watkins <git@mikewatkins.ca> --- Further looking into this reveals that other non-trivial Go application bui= lds fail on Vultr in similar manner until the flag GODEBUG=3Dasyncpreemptoff=3D= 1 is included. The exact module where compile fails varies; successful builds are cached, = so the next failure will be unpredictable.=20 The VM was constructed from a 14.1-RELEASE ISO, nothing special. 2 vCPUs, 2= GB RAM completely under-subscribed. It was then updated to 14.2-RELEASE recent= ly; the problem existed before and after the update and exists using the pkg Go= and the most current version direct from the Go project. A Linux QEMU issue that seems similar: https://github.com/golang/go/issues/69255 >From https://pkg.go.dev/runtime: asyncpreemptoff: asyncpreemptoff=3D1 disables signal-based asynchronous goroutine preemption. This makes some loops non-preemptible for long periods, which may delay GC and goroutine scheduling. This is useful for debugging GC issues because it also disables the conservative stack scanning used for asynchronously preempted goroutines. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283314-42334-HufETADT15>