Displaying 1 result from an estimated 1 matches for "hazardrecognition".
2016 Nov 16
6
[SPARC]: leon2 and leon3: not respecting delayed-write to Y-register
...nough to implement a solution
for this problem.
IMHO the best solution could be to add a pass which checks
whether there are read-hazards after any state-register-writes (Y,
PSR, ASR, WIM, TBR) and which adds NOPs if necessary or even reschedules
other instructions. (Some years ago, there was this
HazardRecognition-class in the scheduler which could be used for
that.)
The easy solution would be to simply add three NOPs the moment where
the WRY instruction is added:
https://github.com/llvm-mirror/llvm/blob/master/lib/Target/Sparc/SparcISelDAGToDAG.cpp#L357
I'd appreciate any help and guidances of how...