Jacob Lifshay

@thomcc > > several architectures have hardware support for f128: RISC-V, PowerPC, s390, and probably more. > > I can't say for sure about the other arches, but PowerPC's is...

I would expect `f64e` to be directly equivalent in bit representation, ABI, and layout to C/C++'s `long double` except in cases like MSVC on x86_64 where they pick `long double`...

> One interesting side-note: PowerPC v3.0 includes an instruction for converting float types to `f80`, though I think that's the only supported operation. Turns out that the only supported `f80`...

@elecprog on x86_64 both `f32` and `f64` are defined by the ABI to be stored in SSE registers and not in the x87 stack. on x86 32-bit they can be...

Clang just merged support for guaranteed tail-calls: https://reviews.llvm.org/rG834467590842

similar idea, but goes further with separate per-edition symbols that are user accessible from all editions (allowing edition migrated code to use the old function still): https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/Effect.20of.20fma.20disabled/near/274199236

one problem you may run into is that resetting changes multiple bits simultaneously in the grey-counter read and write pointers, so relying on just flip-flops to synchronize the signals won't...

I would think that most SRAMs don't get reset on ASICs either, so that shouldn't interfere with BRAM inference.

Ah, missed that.

you probably wanted the file to be a .md file as opposed to what it currently is: a file with no extension. Also, the Rendered link should probably link to...