[all-commits] [llvm/llvm-project] 77513e: [SPIRV] Add a `SPIRVTypeInst` type with some guard...
Juan Manuel Martinez Caamaño via All-commits
all-commits at lists.llvm.org
Wed Feb 11 03:31:04 PST 2026
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 77513e7d740b37da675eadbc0a80b09624614af6
https://github.com/llvm/llvm-project/commit/77513e7d740b37da675eadbc0a80b09624614af6
Author: Juan Manuel Martinez Caamaño <jmartinezcaamao at gmail.com>
Date: 2026-02-11 (Wed, 11 Feb 2026)
Changed paths:
M llvm/lib/Target/SPIRV/SPIRVGlobalRegistry.h
M llvm/lib/Target/SPIRV/SPIRVISelLowering.cpp
Log Message:
-----------
[SPIRV] Add a `SPIRVTypeInst` type with some guardrails (#179947)
The idea behind this PR is to propose a type that we can deploy
gradually to add some guardrails and enforce invariants in the SPIRV
backend.
The PR has 3 commits:
* A first commit where the `SPIRVTypeInst` type is proposed. It's just a
wrapper around `MachineInstr` that adds an assert to check that a
`SPIRVTypeInst` defines a register with the type register class.
* A second commit that shows how the migration could look like for a
single function.
* A third commit that motivates why: we have a `SPIRVType *TypeInst`
that never defines a type in a function whose intention looks very
confusing.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list