vicuna Illegal configuration created by config.mk

Hi @michael-platzer,

when using the VPORT_POLICY=many policy, the Makefile can generate configurations where the maximum PIPE_W is equal to VREG_W. When one PIPE_W is equal to VREG_W then the MAX_OP_W of one vproc_pipeline is also equal to VREG_W. This will trigger the fatal error below: https://github.com/vproc/vicuna/blob/d3c1cf85355ec2b6c0357f23e94f46fe8ceb9dac/rtl/vproc_pipeline.sv#L98-L102

The following lines in the config.mk cause this "issue": https://github.com/vproc/vicuna/blob/d3c1cf85355ec2b6c0357f23e94f46fe8ceb9dac/config.mk#L37 https://github.com/vproc/vicuna/blob/d3c1cf85355ec2b6c0357f23e94f46fe8ceb9dac/config.mk#L67-L70

Jun 27 '22 07:06 moimfeld

@moimfeld Thanks for reporting! Two units are still causing problems when the operand width equals the register width, but I am working on resolving this and will then change this fatal error to only trigger if the operand width is larger than VREG_W.

Jul 04 '22 14:07 michael-platzer

@moimfeld Thanks for reporting! Two units are still causing problems when the operand width equals the register width, but I am working on resolving this and will then change this fatal error to only trigger if the operand width is larger than VREG_W.

Did you solved it ? Please let me know.

Mar 15 '24 06:03 Aravind-kris