diff options
| author | Aldy Hernandez <aldyh@redhat.com> | 2022-10-11 11:20:25 +0200 |
|---|---|---|
| committer | Aldy Hernandez <aldyh@redhat.com> | 2022-10-11 15:52:24 +0200 |
| commit | ad7cff63de618ed723e5df68f0cc9e950d5769e3 (patch) | |
| tree | ed823ce9c60368dd33ab8dd8c0032ec8323cd31e /gcc/value-range.h | |
| parent | 0fa35c7e2974a22b2107fa378895c3069fe07ff3 (diff) | |
| download | gcc-ad7cff63de618ed723e5df68f0cc9e950d5769e3.zip gcc-ad7cff63de618ed723e5df68f0cc9e950d5769e3.tar.gz gcc-ad7cff63de618ed723e5df68f0cc9e950d5769e3.tar.bz2 | |
Move TRUE case first in range-op.cc.
It's incredibly annoying that some of the BRS_TRUE cases come after
BRS_FALSE, if only because we're not consistent. Having random
ordering increases the changes of thinkos when adapting the irange
code to floats.
gcc/ChangeLog:
* range-op.cc (operator_equal::op1_range): Move BRS_TRUE case up.
(operator_lt::op2_range): Same.
(operator_le::op2_range): Same.
(operator_gt::op2_range): Same.
(operator_ge::op2_range): Same.
Diffstat (limited to 'gcc/value-range.h')
0 files changed, 0 insertions, 0 deletions