Michael Pratt
Michael Pratt
cc @golang/runtime
@distancesprinter > I am running Windows Server 2019 Standard (Desktop Experience) in a bhyve VM. "In a bhyve VM" stands out to me here as the most non-standard component. Have...
@RichieSams Do I understand correctly that your crashes are occurring on bare-metal AMD machines?
Indeed, the mismatch is suspicious, but there could be different issues. e.g., it looks like you have only gotten "mcall called on m->g0 stack" and "morestack on g0", while @RichieSams...
Seems possible. This program seems to use Windows API callbacks (https://github.com/saltosystems/winrt-go/blob/main/windows/foundation/asyncoperationcompletedhandler.go#L45), which should be OK, but perhaps something odd is going on. @johnb8 Is is possible for you to try...
cc @hyangah
cc @golang/runtime @golang/android
> Given all of this, I think we could make testing.B.Loop target a real time rather than a benchmark time. Are you imagining some sort of limit on this? It...
Personally I feel like Keep on every function argument and return is overly aggressive. In particular, I think I'd find it annoying to have intermediate values (e.g., return from one...
I'm not so sure about the "last statement" part. It's not too uncommon for a benchmark loop to end with some kind of "bookkeeping" that would break that check. For...