Chris Fallin

> * Something to get the current frame pointer > * Something to get the current stack pointer > * Something to get the return address of the current function...

Ah, I see! So basically what we need is a "what will the return address be for this call instruction" primitive, is that right? My first instinct would be to...

So I spun on this for a few hours and stopped [here](https://github.com/cfallin/wasmtime/commit/5e5c4057a522b3e7020584a0fcf637d8ae9732b5) at around ~500 LoC across 25 files... adding a notion of callsite labels turns out to be fairly...

Thanks for writing this up and for the discussion in today's Cranelift meeting. I'm not sure yet which approach I favor, but I thought it might be useful to write...

Thank you again @uweigand for the detailed space-exploration here; I need to think more about this. Perhaps we can schedule some more time to talk about it in a Cranelift...

Weighing in a bit late here, sorry (and thank you @uweigand for the detailed analysis as always!) -- I think I'm converging toward the following thoughts: - Indeed, booleans are...

FWIW, this now seems to fully work: various upstream issues seem to have resolved (e.g. asan on aarch64 works now?), and I'm successfully running fuzz jobs on a Linux/aarch64 machine...

Hi all -- I was able to build locally on my M1 system, but wanted to improve the situation in general, so I put together a Homebrew formula over at...

Based on feedback in Homebrew/homebrew-core#101491 it sounds like they want to avoid shipping a whole separate LLVM build, instead including a package that is just the sysroot and some wrappers...

OK, thanks very much -- I'll take a look!