diff options
| author | Andrew Pinski <apinski@marvell.com> | 2023-04-01 22:50:27 +0000 |
|---|---|---|
| committer | Andrew Pinski <apinski@marvell.com> | 2023-04-27 08:00:25 -0700 |
| commit | 5fecfed8788eb114508e36e465147f2bb856fa33 (patch) | |
| tree | 49a4aa2dba82270f060fc6231c51dce8d84b5ac8 /gcc/tree-ssa-phiopt.cc | |
| parent | ba9975a259656d099b67ad2b9c69bf970be2b210 (diff) | |
| download | gcc-5fecfed8788eb114508e36e465147f2bb856fa33.zip gcc-5fecfed8788eb114508e36e465147f2bb856fa33.tar.gz gcc-5fecfed8788eb114508e36e465147f2bb856fa33.tar.bz2 | |
MIN/MAX should be treated similar as comparisons for trapping
While looking into moving optimizations from minmax_replacement
in phiopt to match.pd, I Noticed that min/max were considered
trapping even if -ffinite-math-only was being used. This changes
those expressions to be similar as comparisons so that they are
not considered trapping if -ffinite-math-only is on.
OK? Bootstrapped and tested with no regressions on x86_64-linux-gnu.
gcc/ChangeLog:
* rtlanal.cc (may_trap_p_1): Treat SMIN/SMAX similar as
COMPARISON.
* tree-eh.cc (operation_could_trap_helper_p): Treate
MIN_EXPR/MAX_EXPR similar as other comparisons.
Diffstat (limited to 'gcc/tree-ssa-phiopt.cc')
0 files changed, 0 insertions, 0 deletions