search for: orderedinstruct

On 09/27/2018 12:24 AM, Chris Lattner via llvm-dev wrote: On Sep 26, 2018, at 11:55 AM, Reid Kleckner <rnk at google.com<mailto:rnk at google.com>> wrote: As suggested in the bug, if we were to rewrite these passes to use MemorySSA, this bottleneck would go away. I rebased a patch to do that for DSE, but finishing it off and enabling it by default is probably out of scope for me.

On Mon, Sep 24, 2018 at 10:07 PM Chris Lattner <clattner at nondot.org> wrote: > > On Sep 24, 2018, at 9:54 PM, Chris Lattner <clattner at nondot.org> wrote: > >> I think we have consensus that we should go forward with this. Would > anyone mind formally stamping it in phab? So far everyone understandably > has said "makes sense to me, but I don't

...ites aside, dominance seems like a pretty common query. We have several somewhat overlapping mechanisms for checking dominance: - DominatorTree::dominates(Instruction*,Instruction*), the original interface, widely known as a bottleneck - OrderedBasicBlock, as used by memdep, my motivating example - OrderedInstructions, uses OrderedBasicBlock, used by GVN and others - MemorySSA has a similar ordering of memory values that is also invalidated when inserting memory defs. I may have misunderstood how this works, though. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://li...