Displaying 3 results from an estimated 3 matches for "updatereachableedg".
Did you mean:
updatereachableedge
2016 Dec 28
0
Call for testing/heads-up: NewGVN
...all caused by a set of failures to properly mark memory users as
changed in some cases, and to initialize the memory operand equivalence
table properly.
I'm thinking how best to solve it.
In the meantime, reverting the store equivalence changes should fix most of
it (there is one other bug in updateReachableEdge that won't fix, where it
misses marking memoryphi's)
On Tue, Dec 27, 2016 at 3:34 PM, Daniel Berlin <dberlin at dberlin.org> wrote:
>
>
> On Tue, Dec 27, 2016 at 3:22 PM, Nemanja Ivanovic via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> I assume...
2016 Dec 28
1
Call for testing/heads-up: NewGVN
...res to properly mark memory users as
> changed in some cases, and to initialize the memory operand equivalence
> table properly.
>
> I'm thinking how best to solve it.
> In the meantime, reverting the store equivalence changes should fix most
> of it (there is one other bug in updateReachableEdge that won't fix, where
> it misses marking memoryphi's)
>
>
> On Tue, Dec 27, 2016 at 3:34 PM, Daniel Berlin <dberlin at dberlin.org>
> wrote:
>
>>
>>
>> On Tue, Dec 27, 2016 at 3:22 PM, Nemanja Ivanovic via llvm-dev <
>> llvm-dev at lists....
2016 Dec 27
2
Call for testing/heads-up: NewGVN
On Tue, Dec 27, 2016 at 3:22 PM, Nemanja Ivanovic via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I assume that this passes all the lit/lnt test cases on the platform that
> the developers work on.
>
Yes
I bootstrap/test it.
> It causes 31 lnt test case failures on PPC. I've opened a bug with the one
> that is easiest to reduce.
> Also, I'm happy to assist