If amdgpu-unsafe-fp-atomics is specified, allow {flat|global}_atomic_add_f32 even if atomic modes don't match.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
llvm/lib/Target/AMDGPU/SIISelLowering.cpp | ||
---|---|---|
11775–11777 | Should sink this down to be the final check |
Comment Actions
That is the safest thing to do. However, I'm now hearing some thinking that memory likely to be targeted by f.p. atomics is likely to be cached. But again, better to be safe at least until we're clear this will always be the case.
llvm/lib/Target/AMDGPU/SIISelLowering.cpp | ||
---|---|---|
11775–11777 | The idea was to hide the string attribute lookup as the final check. as in !fpModeMatchesGlobalFPAtomicMode(RMW) && attributeStuff() |
llvm/lib/Target/AMDGPU/SIISelLowering.cpp | ||
---|---|---|
11776–11778 | I believe condition should be "or", not "and". Expand if either is not satisfied. |
Should sink this down to be the final check