Preparatory refactoring for the upcoming support of new range check form
to parse.
With this change we always set Index and End values together in the same
place.
parseRangeCheckICmp specification updated.
Paths
| Differential D154156
[IRCE][NFC] Set Index and End together inside parseRangeCheckICmp ClosedPublic Authored by aleksandr.popov on Jun 29 2023, 2:41 PM.
Details Summary Preparatory refactoring for the upcoming support of new range check form With this change we always set Index and End values together in the same parseRangeCheckICmp specification updated.
Diff Detail Event Timelinealeksandr.popov added reviewers: skatkov, apilipenko, anna, DaniilSuchkov, mkazantsev.Jun 30 2023, 12:23 AM Comment Actions LGTM with nit.
This revision is now accepted and ready to land.Jul 2 2023, 9:29 PM aleksandr.popov marked an inline comment as done. Closed by commit rGf56e84736297: [IRCE][NFC] Set Index and End together inside parseRangeCheckICmp (authored by aleksandr.popov). · Explain WhyJul 4 2023, 1:44 AM This revision was automatically updated to reflect the committed changes.
Revision Contents
Diff 536963 llvm/lib/Transforms/Scalar/InductiveRangeCheckElimination.cpp
|
According to specification of this method if we return false, Index and End must be set to nullptr. I do not see this in the code.
Could please update specification or change to implementation accordingly.
I see only one usage of this method and it does not require to set Index and End to nullptr, so I guess that updating of specification is a right way to go.