There is some pointer simplification code originally from isKnownNonNull
that is now better suited to be in isKnownNonZeroFromOperator.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Unit Tests
Time | Test | |
---|---|---|
310 ms | x64 debian > Clang.Modules::stress1.cpp | |
1,090 ms | x64 windows > Clang.Modules::stress1.cpp |
Event Timeline
Comment Actions
No complaints about the code, but just curious whats the rationale? Why is isKnownNonZeroFromOperator a better home?
Comment Actions
For AllocaInst, isKnownNonZeroFromOperator now holds the big switch with all the instruction types so it makes more sense to me for it to be in there.
For CallBase, I think it is better if the code is combined with the rest of the CallInst handling that is already there.
Alloca always returns a pointer.