"isel" is a misleading name
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
Why do other targets do this? -debug already behaves weirdly since -debug prints more during SelectionDAG than -debug-only=isel, and this will make that worse?
Other targets don't have a *-isel pass. I am unclear why AMDGPU has the isel that misguided people to do things like -stop-after=isel (which does not work if they don't build the AMDGPU target)
This sounds broken. The target "owns" the isel pass, so I would expect every target to call this isel, and it wouldn't matter what target you're using
LGTM. The pass name system here is really broken. I don't see how this would break -stop-after without building the target
Thanks. It is just that the pass name does not have a namespace... AMDGPU used the generic name "isel" which might make people confused.
If they don't build the AMDGPU target and think "isel" is a valid pass:
% llc -stop-after=isel -o - test/CodeGen/AArch64/sdag-store-merging-bug.ll LLVM ERROR: "isel" pass is not registered.