Turns out a 380MB html file full of debugging logs is too darn large for Chrome, even on a 96GB laptop. Safari's not given up yet, but hasn't succeeded, but Firefox actually did it.
And the answer is, "R3", duh, in code THAT I WROTE in an earlier CL in the stack (line 310): https://go-review.googlesource.com/c/go/+/636838/2/src/cmd/internal/obj/arm64/obj7.go
"We're trying to find the guy who did this."
BTW we have awesome tools to help with this debugging. I used "bisect" to pinpoint the fault, automatically.
=> View attached media | View attached media | View attached media
=> More informations about this toot | More toots from dr2chase@ohai.social
By-the-way, to bisect-debug this code, I had to add an if and a return in the right place (last chance to do new or old behavior), at line 969 and line 970 here (https://go-review.googlesource.com/c/go/+/636839/3/src/cmd/compile/internal/ssa/regalloc.go), rebuilt the compiler, and then I took the failing test, prefixed it with "bisect " (the command) and added the horrible compiler command line flag
" -gcflags=all=-d=gossahash=PATTERN"
and after that it was all automated, I watched The Expanse while it worked.
=> More informations about this toot | More toots from dr2chase@ohai.social
text/gemini
This content has been proxied by September (ba2dc).