Branch: refs/heads/master
Revision: d0c5909
Author: bradcray
Log Message:
Merge pull request #17808 from bradcray/keep-checks-on-for-range-bounds-check-tests
Keep checks on for tests that are sensitive to range bounds checking
[trivial, not reviewed]
Here, I'm fixing my classic error of checking in tests that perform
runtime checks, that fail under --fast because the checks have been
turned off. I took the approach of forcing checks on for each of
these cases.
The printModuleInitOrder and countDeadModules cases are a bit funny
because they are now sensitive to whether or not checking is on
because the only thing they require from Types.chpl is the safeCast()
check which is completely inlined when checks are off, but has a
helper routine that is not when checks are on. So here, I just forced
the relevant checks to be on as well.
Modified Files:
A test/modules/sungeun/init/printModuleInitOrder.compopts
M test/optimizations/deadCodeElimination/elliot/countDeadModules.compopts
M test/types/range/elliot/rangeLength/rangeLengthOverflow.compopts
M test/types/range/elliot/rangeLength/rangeLengthOverflow2.compopts
M test/types/range/elliot/rangeLength/uintRangeLength.compopts
Compare: https://github.com/chapel-lang/chapel/compare/5b2fef5fb3ae...d0c59096cf17