cherrymui
cherrymui
> Couldn't we simply continue after the call to morestack? That could be a possibility. That would make `morestack` a bit different from other architectures. For example, currently `morestack`never returns,...
Pure-Go binaries are usually statically linked, but cgo binaries are often dynamically linked. Both the `os/exec` test and the `go` command are cgo binaries (due to e.g. the use of...
Thanks for the investigation. I think the Go runtime only installs sigaltstack if it is not already installed. So if a sigaltstack is active, Go wouldn't change it. Yeah, it...
Dup of #66474
cc @dsnet @bradfitz
Thanks for the proposal. > The current framework is a bit complicated, not easy to understand, maintain and extend. I think this is subjective. That said, I agree that the...
Yeah, I think we can start with ARM64. If there is anything that PPC64 or other architecture needs, it is probably a good time to bring it up now. Then...
I think it is okay to change the printing or adjusting tests, if the instructions have the same semantics. Rewriting a Prog to other Prog (or Progs) is more of...
Thanks all, especially @mmcloughlin, for the interesting discussion about avo and machine readable instruction data! As @erifan mentioned that currently there isn't such data, I wonder if a better option...
> maybe we need to update the regexp to only match fatal error: at the start of a line? Makes sense. Done. Thanks.