https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114582
--- Comment #6 from Ian Lance Taylor ---
There is no floating-point in the user code, but Go does have a runtime that
runs at the start of every program, and it is possible that that code uses some
floating-point operations. In particular by
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114582
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114582
--- Comment #3 from Ian Lance Taylor ---
*** Bug 114583 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114582
--- Comment #4 from Ian Lance Taylor ---
*** Bug 114584 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114582
--- Comment #2 from Ian Lance Taylor ---
*** Bug 114581 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114582
--- Comment #1 from Ian Lance Taylor ---
The bug here, and also with PR 114581, is in unwinding from a signal call. A
simplified version of the code for this issue is:
func main() {
defer func() { recover() }()
f()
}
func f() { *p =
