[Bug tree-optimization/83073] Range for VR_VARYING | [1, 1]

[Bug tree-optimization/83073] Range for VR_VARYING | [1, 1]

[amacleod at redhat dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83073

Andrew Macleod <amacleod at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amacleod at redhat dot com

--- Comment #4 from Andrew Macleod <amacleod at redhat dot com> ---
I added a patch to 83072 in which multi-range will now recognize there is no
[0,0] in  x|1.

When we add bitmask tracking to ranger, it is in the work queue to track both
must-be-zero and must-be-one bits, and integrate that knowledge with range
queries.  
(so if (x == 20) would be known false after x = x | 1)

Any additional input on what kind of other information could be attached here
to this PR.

[Bug tree-optimization/83073] Range for VR_VARYING | [1, 1]

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83073

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Take -O2 -fno-tree-fre -fno-tree-ccp -fno-tree-forwprop:
int f(int x)
{
    x = x|1;
    return x & 1;
}

We should be able to figure this out in evrp but don't currently.

VRP can figure it out as it does a match and simplify for the statement.

[Bug tree-optimization/83073] Range for VR_VARYING | [1, 1]

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83073

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |missed-optimization
           Severity|normal                      |enhancement

[Bug tree-optimization/83073] Range for VR_VARYING | [1, 1]

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83073

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>:

https://gcc.gnu.org/g:49d5fb4feee831868d80fff4d024c271911c92ca

commit r12-6559-g49d5fb4feee831868d80fff4d024c271911c92ca
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Wed Jan 12 13:31:08 2022 -0500

    Allow more precision when querying from fold_const.

    fold_const::expr_not_equal_to queries for a current range, but still uses
    the old value_range class.  This is causing it to miss opportunities when
    ranger can provide something better.

            PR tree-optimization/83072
            PR tree-optimization/83073
            PR tree-optimization/97909
            gcc/
            * fold-const.c (expr_not_equal_to): Use a multi-range class.

            gcc/testsuite/
            * gcc.dg/pr83072-2.c: New.
            * gcc.dg/pr83073.c: New.

[Bug tree-optimization/83073] Range for VR_VARYING | [1, 1]

[amacleod at redhat dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83073

Andrew Macleod <amacleod at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Andrew Macleod <amacleod at redhat dot com> ---
Ranger VRP also does match and simplify now for both EVRP and VRP2.