iximeow

typo? maybe?

1

pretty sure it should be this one and not the other one

SIGSEGV during compilation when taking address of extern x86-interrupt fn

2

```rust #![feature(abi_x86_interrupt)] #[repr(C)] pub struct Context rustc crash.rs Segmentation fault (core dumped) ``` Interestingly, it seems like `#[repr(C)]` is load-bearing? No crash without a `repr` on the argument type. Also...

the docs on `Inst` note that the type is returned by non-resultful instructions built from `InstBuilder`, but did _not_ note that it is also returned by `call` and `call_indirect`. if...

Refactor/rename parts of Context?

3

### The Context (for `Context`) I've had a nagging feeling something is a little "off" about `Context` since we had to add [parent_ctx](https://github.com/bytecodealliance/lucet/blob/master/lucet-runtime/lucet-runtime-internals/src/context/mod.rs#L122).. I said I'd ruminate on this back...

It turns out trying to use `lld` as an alternate linker causes some issues for Lucet. One is possibly an `lld` bug. The other is, I think, somewhere in our...

[WIP] Lucet i686 (32-bit x86) support... ish

2

First, why `i686`? `i386` has, at best, the x87 FPU for floating point operations. I'm pretty sure `i686` implies processors recent enough to have MMX/SSE, so our floating point stuff...

add option to report timing, as well as reporting time taken to output

1

Adds a `--report-times` which makes for nice breakdowns via `lucetc --report-times slow_to_compile.wat` like: ``` ======== ======== ================================== Total Self Pass -------- -------- ---------------------------------- 0.000 0.000 Translate WASM module 0.001 0.001...

lucet-runtime will panic on hosts that don't use 4kb pages, which has been discussed a bit [here](https://github.com/bytecodealliance/lucet/pull/514#issuecomment-626935637). I'm lightly optimistic that adapting lucet-runtime to non-4kb page assumptions might be sufficient...

This was demonstrated at one point through https://github.com/bytecodealliance/lucet/pull/375, but that was an unconditional change that didn't make sense to land on its own - how do we feel about a...

suboptimal codegen when initializing an array of padded structs

1

in the following code, `reset_implicit_padding` generates somewhat worse assembly under `-C opt-level=3` than `reset_explicit_padding`. with explicit padding generates to a `memset` - i'd hoped both would `memset`: ```rust #[repr(Rust, align(2))]...