Lofty

So, the PS2, which I've been developing on, has a hardware requirement for 16-byte aligned DMA (it ignores the lower four bits of the specified memory address). For the sake...

I think I might have gotten something similar to this bug? Without `-update-debug-sections`, this works: ``` $ /home/lofty/llvm-project/llvm-install/bin/llvm-bolt -instrument /home/lofty/test/yukari/target/x86_64-unknown-linux-gnu/release/yukari --instrumentation-file-append-pid --instrumentation-file /home/lofty/test/yukari/target/bolt-profiles/yukari/profile -o /home/lofty/test/yukari/target/x86_64-unknown-linux-gnu/release/yukari-bolt-instrumented BOLT-INFO: shared object or position-independent...

``` BOLT-INFO: shared object or position-independent executable detected BOLT-INFO: Target architecture: x86_64 BOLT-INFO: BOLT version: 6b3bc7cd3c6f56a63f97e71dc236b2281d98d9d1 BOLT-INFO: first alloc address is 0x0 BOLT-INFO: creating new program header table at address...

Rust code: ```rust fn main() { println!("Hello, world!"); } ``` Build command was `RUSTFLAGS="-Clink-args=-Wl,-q" cargo +nightly-2022-08-06 build --release` as above. llvm-dwarfdump: ``` 0x0000054b: DW_TAG_compile_unit DW_AT_stmt_list (0x00000111) DW_AT_ranges (0x0000000c [0x0000000000006000, 0x0000000000006016)...

What about the DE10-Nano and MiSTer situation? The latter is basically a board mounted on the former, and so pins which are free connectors on the DE10 are instead Resources...

Alternatively, even a differential between current and last calculation would be nice for this, to get an idea of whether we're getting closer or further from the optimum.

Apologies for the grave digging, but this is actually the approach I'm using for my PS2 emulator. It seems to work okay for cold code, but (at least for my...

I think proposal 1 is the best option. The use of a shape as a target size in prop 2 and 3 makes me uncomfortable: consider somebody who knows that...

There... are no truncation overflow checks proposed? Aside from a guard against truncating to a wider value than what you started with. As for `range`/enum casting being misleading, there seems...

When matching against a Python integer, one would use something like `m.Case(0bxy)`, where x is most significant first, so it seems most natural to me to have the leftmost bit...