Jacob Lifshay
Jacob Lifshay
Clean up some formatting as well
See https://github.com/m-labs/nmigen/issues/141#issuecomment-509985372 for motivation Todo list (edit as needed to keep up to date): - [ ] fix failing tests - [ ] enable requiring pypy3 to pass in .travis.yml
I have a `Path` for an enum variant like `my_mod::MyType::MyVariant`, and I can remove the `MyVariant` part with `path.segments.pop()`, however that gives me a path like `my_mod::MyType::` which is syntatically...
I noticed that the `i64.atomic.wait` instruction can't be translated directly to the `futex` syscall on Linux, since Linux only supports 32-bit `futex` operations. I'm concerned that non-web embeddings on Linux...
in , the ICD functions should be `extern "system"` instead of `extern "C"` since, on 32-bit windows, they are `stdcall`. I'm not sure what to do about the hard float...
Things like `impl BitAndAssign for BigInt` are missing.
I wrote Rust bindings to softfloat (https://crates.io/crates/softfloat-sys), however I ran into linking problems since a lot of internal functions are declared inline but there is no out-of-line version of them....
the fmadd group of instructions should use f32MulAdd rather than f32Mul then f32Add
I'm using toml 0.10.1 downloaded from PyPI on CPython 3.8.0 on Linux. My code: ```python3 import toml for i in range(1, 8): v = "12:34:56." + "1234567"[:i] print(v, toml.loads("a=" +...
I'm working on an initial draft design for some new PowerPC instructions that handles wasm memory32/64 load/store with hardware-level address range checking and base address addition: https://bugs.libre-soc.org/show_bug.cgi?id=585 comments/questions/contributions welcome!