diff options
| author | Richard Sandiford <richard.sandiford@arm.com> | 2024-10-24 14:22:30 +0100 |
|---|---|---|
| committer | Richard Sandiford <richard.sandiford@arm.com> | 2024-10-24 14:22:30 +0100 |
| commit | 3e93828e601c62176ea2b4a1dd0b5a1db5657a8e (patch) | |
| tree | 5da2f31d92daecbf68db80897b963d0a7ff2c5ab /gcc/gcc-urlifier.cc | |
| parent | f24e10876689dcd92b05756bd3ec833ddf1e6b7e (diff) | |
| download | gcc-3e93828e601c62176ea2b4a1dd0b5a1db5657a8e.zip gcc-3e93828e601c62176ea2b4a1dd0b5a1db5657a8e.tar.gz gcc-3e93828e601c62176ea2b4a1dd0b5a1db5657a8e.tar.bz2 | |
Make more places handle exact_div like trunc_div
I tried to look for places where we were handling TRUNC_DIV_EXPR
more favourably than EXACT_DIV_EXPR.
Most of the places that I looked at but didn't change were handling
div/mod pairs. But there's bound to be others I missed...
gcc/
* match.pd: Extend some rules to handle exact_div like trunc_div.
* tree.h (trunc_or_exact_div_p): New function.
* tree-ssa-loop-niter.cc (is_rshift_by_1): Use it.
* tree-ssa-loop-ivopts.cc (force_expr_to_var_cost): Handle
EXACT_DIV_EXPR.
Diffstat (limited to 'gcc/gcc-urlifier.cc')
0 files changed, 0 insertions, 0 deletions