| commit | 45ef24f2702dac4f8707ca682ed364019ee90c44 | |
| author | Aldy Hernandez <aldyh@redhat.com> | |
| Fri, 10 May 2024 21:21:29 +0000 (10 23:21 +0200) | ||
| committer | Aldy Hernandez <aldyh@redhat.com> | |
| Sat, 11 May 2024 09:15:50 +0000 (11 11:15 +0200) | ||
| tree | 2fb98b904431e85e1e71a0679016caa109b9bc16 | treesnapshot (tar.gz zip) |
| parent | 3dab8f8a542aeabfab1a244a7a601b220680c80b | commitdiff |
[prange] Do not trap by default on range dispatch mismatches.
The trap in the range-op dispatch code is really an internal debugging
aid, and only a temporary one for a few weeks while the dust settles.
This patch turns it off by default, allowing problematic passes to
turn it on for analysis.
gcc/ChangeLog:
* range-op.cc (TRAP_ON_UNHANDLED_POINTER_OPERATORS): New
(range_op_handler::fold_range): Use it.
(range_op_handler::op1_range): Same.
(range_op_handler::op2_range): Same.
(range_op_handler::lhs_op1_relation): Same.
(range_op_handler::lhs_op2_relation): Same.
(range_op_handler::op1_op2_relation): Same.
The trap in the range-op dispatch code is really an internal debugging
aid, and only a temporary one for a few weeks while the dust settles.
This patch turns it off by default, allowing problematic passes to
turn it on for analysis.
gcc/ChangeLog:
* range-op.cc (TRAP_ON_UNHANDLED_POINTER_OPERATORS): New
(range_op_handler::fold_range): Use it.
(range_op_handler::op1_range): Same.
(range_op_handler::op2_range): Same.
(range_op_handler::lhs_op1_relation): Same.
(range_op_handler::lhs_op2_relation): Same.
(range_op_handler::op1_op2_relation): Same.
| gcc/range-op.cc | diffblobblamehistory |