Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-06-10 Thread Richard Biener via Gcc-patches
On Wed, Jun 9, 2021 at 5:24 PM Andrew MacLeod wrote: > > On 6/9/21 7:48 AM, Richard Biener wrote: > > On Tue, Jun 8, 2021 at 4:48 PM Andrew MacLeod wrote: > >> > >> > >> Richard. > >> > Andrew > > >> OK, so this would be the simple way I'd tackle this in gcc11. This > >> should be

Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-06-09 Thread Andrew MacLeod via Gcc-patches
On 6/9/21 7:48 AM, Richard Biener wrote: On Tue, Jun 8, 2021 at 4:48 PM Andrew MacLeod wrote: Richard. Andrew OK, so this would be the simple way I'd tackle this in gcc11. This should be quite safe. Just treat debug_stmts as if they are not stmts.. and make a global query. EVRP will

Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-06-09 Thread Richard Biener via Gcc-patches
On Tue, Jun 8, 2021 at 4:48 PM Andrew MacLeod wrote: > > On 6/2/21 3:29 AM, Richard Biener wrote: > > On Tue, Jun 1, 2021 at 4:24 PM Andrew MacLeod wrote: > >> On 6/1/21 3:34 AM, Richard Biener wrote: > >>> On Tue, Jun 1, 2021 at 3:38 AM Andrew MacLeod via Gcc-patches > >>> wrote: > An

Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-06-08 Thread Andrew MacLeod via Gcc-patches
On 6/2/21 3:29 AM, Richard Biener wrote: On Tue, Jun 1, 2021 at 4:24 PM Andrew MacLeod wrote: On 6/1/21 3:34 AM, Richard Biener wrote: On Tue, Jun 1, 2021 at 3:38 AM Andrew MacLeod via Gcc-patches wrote: An ongoing issue is the the order we evaluate things in can affect decisions along the

Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-06-02 Thread Richard Biener via Gcc-patches
On Tue, Jun 1, 2021 at 4:24 PM Andrew MacLeod wrote: > > On 6/1/21 3:34 AM, Richard Biener wrote: > > On Tue, Jun 1, 2021 at 3:38 AM Andrew MacLeod via Gcc-patches > > wrote: > >> An ongoing issue is the the order we evaluate things in can affect > >> decisions along the way. As ranger isn't a

Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-06-01 Thread Andrew MacLeod via Gcc-patches
On 6/1/21 3:34 AM, Richard Biener wrote: On Tue, Jun 1, 2021 at 3:38 AM Andrew MacLeod via Gcc-patches wrote: An ongoing issue is the the order we evaluate things in can affect decisions along the way. As ranger isn't a fully iterative pass, we can sometimes come up with different results if

Re: [PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-06-01 Thread Richard Biener via Gcc-patches
On Tue, Jun 1, 2021 at 3:38 AM Andrew MacLeod via Gcc-patches wrote: > > An ongoing issue is the the order we evaluate things in can affect > decisions along the way. As ranger isn't a fully iterative pass, we can > sometimes come up with different results if back edges are processed in >

[PATCH] PR tree-optimization/100781 - Do not calculate new values when evaluating a debug, statement.

2021-05-31 Thread Andrew MacLeod via Gcc-patches
An ongoing issue  is the the order we evaluate things in can affect decisions along the way. As ranger isn't a fully iterative pass, we can sometimes come up with different results if back edges are processed in different orders. One of the ways this can happen is when the cache is