diff options
| author | Kevin P. Neal <kevin.neal@sas.com> | 2022-06-03 14:28:02 -0400 |
|---|---|---|
| committer | Kevin P. Neal <kevin.neal@sas.com> | 2022-06-06 09:24:11 -0400 |
| commit | a1f1bd547b0d4c4b200dd485b85366bcd24c84c0 (patch) | |
| tree | 83b4d2dd3d4c773b689cdef071150b7280d94d58 /llvm/lib/CodeGen/ModuloSchedule.cpp | |
| parent | c2e3e91ddec002ac2514708867153e5f6b03dc48 (diff) | |
| download | llvm-a1f1bd547b0d4c4b200dd485b85366bcd24c84c0.zip llvm-a1f1bd547b0d4c4b200dd485b85366bcd24c84c0.tar.gz llvm-a1f1bd547b0d4c4b200dd485b85366bcd24c84c0.tar.bz2 | |
[IPSCCP] Switch away from Instruction::isSafeToRemove()
In D115737 I found that I needed to teach Instruction::isSafeToRemove()
about strictfp/constrained intrinsics. It was pointed out that this is
probably the wrong function to use isInstructionTriviallyDead(). It doesn't
make sense to have a "second, worse implementation".
I also believe that the Instruction class is the wrong place for this
functionality. The information about whether or not an instruction can be
removed is in the transform passes and should stay there.
Differential Revision: https://reviews.llvm.org/D118387
Diffstat (limited to 'llvm/lib/CodeGen/ModuloSchedule.cpp')
0 files changed, 0 insertions, 0 deletions