Anton Kirilov

@alexcrichton I added you as reviewer for the Wasmtime bits.

@alexcrichton I wanted to finish with the pointer authentication PR before coming back to this one: > * If a module is compiled with bti support and loaded into an...

@cfallin I think that I have resolved all of @alexcrichton's comments that are related to Wasmtime, so do you have any feedback on the Cranelift side of things?

> The next question is, how to characterize the two "lane order" options for values in registers. First, we notice that if the vector is interpreted as `I128`, there is...

@uweigand Are you aware of PR #4820? IMHO the only difference between `bitcast` and `raw_bitcast` is that the latter is allowed to change the number of lanes (while still keeping...

Ah, I see, my memory is fuzzy, and I feel that this was discussed before, but is the boolean thing basically the only real reason for the distinction between `bitcast`...

Unfortunately the requirement that unaligned atomic memory accesses trap implies that an explicit alignment check would be pretty much mandatory (unless it could be optimized out) when targeting many current...

> Would it make sense to add two bool fields for augmentation characters? Either option looks fine to me.

Another useful call frame instruction that is a GNU extension is `DW_CFA_GNU_window_save` - the reason is that it has an [alias](https://github.com/ARM-software/abi-aa/blob/2021Q3/aadwarf64/aadwarf64.rst#call-frame-instructions-beta), `DW_CFA_AARCH64_negate_ra_state`, which is necessary to support unwinding through functions...

Also, you can try: `nm -D --with-symbol-versions /lib64/libc.so.6 | grep __cxa_thread_atexit_impl`