Adam C. Foltzer

Results 40 issues of Adam C. Foltzer

The WASI ecosystem is evolving quickly, for example with Rust 1.41.0 using `wasi_snapshot_preview1` rather than `wasi_unstable`. To keep up, we are going to either have to keep moving to the...

... and possibly statically, but I haven't checked yet. The problem is that the thread-local variable `CURRENT_INSTANCE`, defined in `lucet-runtime-internals`, ends up appearing in both `liblucet-runtime.so` and `liblucet-wasi.so`, but at...

There is at least one key difference: `alignof(long long) == 4` with `clang -m32`, but `alignof(long long) == 8` with `wasi-sdk/bin/clang`. While I'm not convinced that all of our recent...

#408 solved the immediate problem of `lucetc` not offering useful error messages, but there are other crates that likely need the same treatment. We also should make error messages part...

`--opt-level {0,1,2}` work fine, but none of the other options are recognized despite being described in the help text. It'd probably also be nice to allow a short option from,...

If, when handling a signal, we are using either the default behavior (fault returning) or the terminating behavior, there is a context switch and execution continues back at the host....

We of course don't need to adopt the suggestions whole cloth, but we should see whether we can get a good signal-to-noise ratio coming from Clippy.

This is useful when you don't necessarily want to consume the entire stream as a reader, but still want to retain the stream for other uses. ~The nested tuple/`Option`/tuple is...

S-waiting-on-author
A-io

Are there any troubleshooting steps you might suggest if I'm getting similar errors to #10 with new versions of `text`? I'm trying to do a shrink, but right now can...

bug
question

`sigaltstack` is part of the `sigaction` family of APIs, used to control which stack signal handlers run on.