stnolting

The standard `C` extension is already implemented (-> `CPU_EXTENSION_RISCV_C` generic). In this particular case `C` = `Zcf`, but all the compressed floating-point operations are mapped to normal integer load/store because...

> bottom line -- Zcb would be first, when we get around to it.... I agree! But before we start implementing that we should wait for GCC support. Unfortunately, upcoming...

Interesting results! Thanks for sharing! 35% would be quite amazing, but I'm not sure what the "cost" of that might be (additional hardware resources, impact on critical path, etc.). `Zcmp`...

Oh, I did not expect that. However, RVA is the [application-class](https://github.com/riscv/riscv-profiles/blob/main/rva23-profile.adoc#rva23-profiles) profile (MMU, 64-bit, ...), which is out of scope of this project right now 🙈 I had another look...

The `Zcmp`'s push/pop instruction are quite powerful as they can "compress" up to 13 load/stores and an addition into a single 16-bit instruction! They might even increase performance a little...

I think this has been answered, e.g. https://github.com/riscv/riscv-isa-manual/issues/414#issuecomment-859706272

> E.g. using '-' for don't care values, while theoretically nice, ends up causing large amounts of 'X' propagation as '-' resolves to 'X' with almost any logical operator. This...

Is this still up-to-date? 🤔 I am trying to constrain the behavior of `mtval`. This is my entry in `*_platform.yaml`: ```yml mtval_condition_writes: implemented: true behaviour: - [0, [0x00000000:0xFFFFFFFF], "Instruction fetch...

> I believe this has not been implemented yet. I already thought so. Anyway, thanks for the fast response! I have tested your code. Unfortunately, my framework version does not...

Thanks for the hint! The syntax errors are resolved now. :+1: --------------------------- However, I cannot modify the model's `mtval` update behavior so that it matches the DUT's one. I am...