Closed paili0628 closed 2 weeks ago
Looking at the test cases, they're failing because static-promotion
doesn't want to promote invoke with comb group
. But I think that was because those comb groups
used to increase the latency (bc they would write into a register). Now I don't think that restriction should apply. In other words, I think it's fine to get rid of that check. Does that make sense?
Looking at the test cases, they're failing because
static-promotion
doesn't want to promoteinvoke with comb group
. But I think that was because thosecomb groups
used to increase the latency (bc they would write into a register). Now I don't think that restriction should apply. In other words, I think it's fine to get rid of that check. Does that make sense?
Wait I don't think we currently have that restriction in static-promotion
?
invoke
-with
should not increase latency anymore; compile-invoke
removes the full construct and inlines the comb group
assignments.
@paili0628 in case you haven't figured out the bug, I did some digging and I think it's here:
comp.go
should be added to outs
. I can add a PR to fix this bug unless you want to do it.
place
compile-invoke
afterstatic-promotion
.This would possibly lead to a few performance drops. Hence this pr aims to investigate into the reasons for the performance drops and try to fix them.