Sure, its a compiler, but integrating the reference SRAMs worked like a charm. Guess I have to try the compiler. It’ll be a bloody Christmas.
Regarding size, I guess it has been discussed here on slack quite a bit already, since many user implement a processor. The register file (e.g. 32x32) is always a classical example for a FF-macro trade-off.
But thinking of it again I guess there are also other arguments. I understand that the flow still has issues with SDFs from macros (e.g. SRAMs) and paths to/from macros are probably (therefore) not considered during timing optimizations, I guess it is fair to say, that you are better off with FF for processor register files at the moment. At least that would save my Cristmas.
It would probably be nice to have a pre-qualified RF size SRAM with 0.5 cycle latency in the future #JustSayingForAFriend.
Thanks a lot,
Cheers, Tobias