Re: [tree-optimization/71947] Avoid unwanted propagations

On 10/12/2016 09:00 AM, Georg-Johann Lay wrote: On 10.10.2016 23:06, Jeff Law wrote: So if we have an equality conditional between A & B, we record into our const/copy tables A = B and B = A. This helps us discover some of the more obscure equivalences. But it also creates problems with an

Re: [tree-optimization/71947] Avoid unwanted propagations

On 10/12/2016 08:36 AM, Christophe Lyon wrote: It fixes the tests from 71947 and 77647 without regressing (obviously). I've included an xfailed test for a more complex situation that we don't currently handle (would require backtracking from the equality comparison through the logicals that

Re: [tree-optimization/71947] Avoid unwanted propagations

On 10.10.2016 23:06, Jeff Law wrote: So if we have an equality conditional between A & B, we record into our const/copy tables A = B and B = A. This helps us discover some of the more obscure equivalences. But it also creates problems with an expression like A ^ B Where we might cprop the

Re: [tree-optimization/71947] Avoid unwanted propagations

Hi Jeff, On 10 October 2016 at 23:06, Jeff Law wrote: > > > So if we have an equality conditional between A & B, we record into our > const/copy tables A = B and B = A. > > This helps us discover some of the more obscure equivalences. But it also > creates problems with an

[tree-optimization/71947] Avoid unwanted propagations

So if we have an equality conditional between A & B, we record into our const/copy tables A = B and B = A. This helps us discover some of the more obscure equivalences. But it also creates problems with an expression like A ^ B Where we might cprop the first operand generating B ^ B