We use use64bitIndex in the option to decide the target device
address bitwidth. This makes it consistent with index type
conversion too.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
The patch LGTM, but I have a design question: have you considered moving PhysicalXY from the module level to target env? I understand that this follows SPIR-V proper, but what do we gain much by keeping those separate?
Comment Actions
Target environment is actually the requirements towards which we are CodeGen, where these Logical/PhysicalNN is the derived module addressing model details to meeting those requirements. Those are part of the final SPIR-V blob; it's more for driver consumption. So I don't think we should require the developer to figure them out; that's the job of the compiler?