Details
- Reviewers
arsenm rampitec nhaehnle - Commits
- rG275ecaae1653: [AMDGPU] Cluster MIMG instructions
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Unit tests: unknown.
clang-tidy: unknown.
clang-format: unknown.
Build artifacts: console-log.txt
Pre-merge checks is in beta. Report issue. Please join beta or enable it for your project.
More generally, I'm worried about whether the generic infrastructure will do something useful with the extra address arguments, so this needs quite a bit of test coverage about what happens with different texture coordinate patterns.
This absolutely needs a test with sampled images.
I've added one.
More generally, I'm worried about whether the generic infrastructure will do something useful with the extra address arguments, so this needs quite a bit of test coverage about what happens with different texture coordinate patterns.
The only code that knows about the address operands is SIInstrInfo::getMemOperandsWithOffset (which produces a list of address operands) and SIInstrInfo::shouldClusterMemOps (which consumes it). The logic is currently very simple: cluster if the first address operand (the image descriptor) is the same.
I'm sure the logic could be much cleverer, but I'd like to leave that for later patches with their own test cases. Until that happens, I'm not sure that it's worth producing tests for different texture coordinate patterns.
llvm/lib/Target/AMDGPU/SIInstrInfo.cpp | ||
---|---|---|
2763 | Braces |
Braces