Connor Horman

> Atomic acquire and release are not typically implemented by flushing caches all the way to main memory; that would make atomic operations outrageously slow And on x86 (or other...

I'm working on a competing compiler to rustc, and I am particularily aiming to make `Box` not magic (the current impl is not even a lang item. It uses an...

To implement it in user code, you'd need placement expressions or some other way to force the compiler into eliding the move and the intermediate value (where possible).

One of the reasons for the box syntax I thought was to allow you to box large values that may cause a stack overflow if an intermediate value is not...

RE. the above (w/ the context from reading the minutes of that aformentioned meeting after the fact), C requires that a status code `0` (and incidentally also `EXIT_SUCCESS` which may...

> More concretely, the idea being that constructing an ExitCode from 0u8 will always give you ExitCode::SUCCESS, and any other value would always give you ExitCode::FAILURE, but ExitCode::SUCCESS doesn't necessarily...

I would assume that the full list of supported abis is an *implementation-defined* (or *unspecified*) set that contains `"Rust"`, `"C"`, and `"system"`. If this is the case, I would recommend...

On Tue, Mar 9, 2021 at 20:06 mcclure ***@***.***> wrote: > We should definitely list out the ABIs that every implementation should > have. Is it just "Rust", "C", and...

I posted this on the tracking issue but it makes sense to cross-post to the RFC. In 32-bit x86 mode, the StackFrame struct can vary dynamically - depending on the...

For w65/65816, I'm working on my own toolchain (including eventually a C compiler, probably gcc). The support is being included in a fork of GNU binutils at https://github.com/chorman0773/binutils-gdb. I think...