Ivor Wanders

> I understand that merging with big changes is tough, sorry for inconvenience. No worries, like I said, this happens sometimes, especially if people develop large changes in parallel! >...

I always thought the fault codes were car and manufacturer specific, either way, thanks for sharing.

Hi, cool to hear you stumbled upon this repo :) There's nothing stopping you from encoding (binary) data into the watermark, you can populate the [MarkBuf](https://github.com/iwanders/spread_spectrum_watermarking/blob/f6f99f085f5da76658d9a11b92b698ccbac23602/src/algorithm.rs#L602-L645) with whatever you want,...

Yeah, I think that's better than trying to encode data into the watermark directly.

I ran into the same high memory usage trying to train my implementation of FCN, using pretty much twice the memory of what pytorch uses: ``` Before forward: 1250MiB/7930MiB After...

Hi @marinjurjevic , I think I ran into the same problem on Debian 12 today. I've filed https://github.com/WerWolv/ImHex/pull/2390 which fixes it for me. 1. I think you can work around...

> because it pre-allocates structures indexed by these IDs. If you provide inaccurate information, the code will panic. > The num_vregs, num_blocks and num_insts methods are perhaps ambiguously named: in...

Okay, I pushed a commit that rewords the documentation and makes the checks check the length. > Non-contiguous ranges, on the other hand, are perfectly fine; the allocator does not...

> Doesn't that assert in InstRange::new() permit a range of 0..0 as it's a 0 stack backtrace: 0: rust_begin_unwind at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library/std/src/panicking.rs:692:5 1: core::panicking::panic_fmt at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library/core/src/panicking.rs:75:14 2: core::panicking::panic at /rustc/4d91de4e48198da2e33413efdcd9cd2cc0c46688/library/core/src/panicking.rs:145:5 3:...

> I want to make sure I have the precise details of your report right: are you somehow reaching this with CLIF ("because I manually hacked up a clif file")?...