search

StanfordAHA / CGRAMapper

CoreIR based mapping tool for CGRA
BSD 3-Clause "New" or "Revised" License
6 stars 4 forks source link

`alu_op_debug` max/smax incorrect #68

Closed Kuree closed 5 years ago

Kuree commented 6 years ago

See https://github.com/StanfordAHA/CGRAMapper/blob/b9ab9079e46dfe9c89b09f33f7bcce5566c5ae11/src/definitions/cgralib_def.h#L39

The debug string should be smax.

I'm wondering what's the future plan for alu_op_debug? It's useful to me since I don't need to regenerate the same string as the mapper already does that. But if you want to remove it in the future, I can copy your code over to my PnR tools. Is there any documentation on how these bits are translated to op str? Thanks.

rdaly525 commented 6 years ago

the alu_op_debug was merely for debugging statements and should not be parsed/used in any way.

I used the PE Spec found https://github.com/StanfordAHA/CGRAGenerator/wiki/Proposed-PE-Spec to generate the bits for the PE.