- Make the SIMemoryLegalizer insertAcquire function be in the same order for each target to be consistent.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
If we're nitpicking over such details, I would point out that it would be better to structure the whole thing differently, with a single legalizer class in which the insertAcquire etc. methods have different paths based on the hardware generation.
The reasoning is that code of the form "gfx10 behaves like gfx7 except ABC, gfx7 behaves like gfx6 except DEF" becomes increasingly difficult to reason about or refactor the more hardware generations we add.