Skip to content

[SPIR-V][Codegen] Represent the property of the target to declare and use typed pointers and update MachineVerifier to use it #110270

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions llvm/include/llvm/CodeGen/TargetLowering.h
Original file line number Diff line number Diff line change
Expand Up @@ -455,6 +455,12 @@ class TargetLoweringBase {
return true;
}

/// Return true if the target can handle the declaration and use of pointers
/// that specify the type of data they point to, meaning that interpretation
/// of the data type is not left to instructions that utilize the pointer, but
/// encoded by the pointer declaration.
virtual bool hasTypedPointer() const { return false; }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this bit be in the Subtarget/Target info?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know what is the best option. After some reflection I decided that the notion of typed pointers seems to be more of a target lowering property than property of the SPIRV target machine itself, especially given the recent appearance of untyped pointers (https://htmlpreview.github.io/?https://github.com/KhronosGroup/SPIRV-Registry/blob/main/extensions/KHR/SPV_KHR_untyped_pointers.html) that do not specify the type of data they point to. Although we can't lower without typed pointers at the moment, probably this property belongs to lowering rather than to target machine. I'm not 100% sure though.


/// Return true if the @llvm.experimental.vector.partial.reduce.* intrinsic
/// should be expanded using generic code in SelectionDAGBuilder.
virtual bool
Expand Down
4 changes: 3 additions & 1 deletion llvm/lib/CodeGen/MachineVerifier.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -1294,7 +1294,9 @@ void MachineVerifier::verifyPreISelGenericInstruction(const MachineInstr *MI) {
report("bitcast sizes must match", MI);

if (SrcTy == DstTy)
report("bitcast must change the type", MI);
if (!SrcTy.isPointer() ||
!MF->getSubtarget().getTargetLowering()->hasTypedPointer())
report("bitcast must change the type", MI);

break;
}
Expand Down
3 changes: 3 additions & 0 deletions llvm/lib/Target/SPIRV/SPIRVISelLowering.h
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,9 @@ class SPIRVTargetLowering : public TargetLowering {
// prevent creation of jump tables
bool areJTsAllowed(const Function *) const override { return false; }

// allow for typed pointers
bool hasTypedPointer() const override { return true; }

// This is to prevent sexts of non-i64 vector indices which are generated
// within general IRTranslator hence type generation for it is omitted.
MVT getVectorIdxTy(const DataLayout &DL) const override {
Expand Down
15 changes: 15 additions & 0 deletions llvm/test/MachineVerifier/SPIRV/test_typedptr_bitcast.mir
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
#RUN: llc -mtriple=spirv64-unknown-unknown -o - -global-isel -run-pass=none -verify-machineinstrs %s 2>&1 | FileCheck %s

---
name: test_typedptr_bitcast
legalized: true
regBankSelected: false
selected: false
tracksRegLiveness: true
liveins:
body: |
bb.0:
; CHECK-NOT: Bad machine code: bitcast must change the type
%0:_(p0) = G_IMPLICIT_DEF
%1:_(p0) = G_BITCAST %0
...
Loading