Skip to content

Removed all floating point related signals and parameters. Removed un…

Eclipse Webmaster requested to merge github/fork/Silabs-ArjanB/ArjanB_xf into main

Created by: Silabs-ArjanB

…used X_REG_WIDTH parameter.

Reason to remove the floating point related signals and parameters is that its inclusion was a bit arbitrary. For example, what if the CPU included a vector register file, should we then also add an interface to such register file to the extension interface?

I think it is cleanest if we define the protocol to only take into account a relatively minimal CPU (RV32I[C]/RV64I[C]). People who use the extension interface and want to use a floating point extension with separate floating point register file can always (and are likely to) add the floating point register file external to the CPU.

Signed-off-by: Arjan Bink Arjan.Bink@silabs.com

Merge request reports

Loading