[llvm-bugs] [Bug 46874] New: GVNHoist hoists a load above a null check

via llvm-bugs llvm-bugs at lists.llvm.org
Tue Jul 28 09:59:46 PDT 2020


            Bug ID: 46874
           Summary: GVNHoist hoists a load above a null check
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: Scalar Optimizations
          Assignee: unassignedbugs at nondot.org
          Reporter: chang-sun.lin.jr at intel.com
                CC: llvm-bugs at lists.llvm.org

Created attachment 23782
  --> https://bugs.llvm.org/attachment.cgi?id=23782&action=edit

In the attached .ll file, GVNHoist hoists a load above its null check.

opt --gvn-hoist hoistbug.ll -S > bad.ll
clang -O0 bad.ll

There are two loads in the function "foo", in different blocks, with the same
address %p. Both load-blocks are guarded by conditional null checks. The first
load-block also has a conditional branch in it that goes directly to the second

  %cmp.not = icmp eq i32* %p, null
  br i1 %cmp.not, label %if.end3, label %if.then

  %0 = load %p…
  br … %if.end3, %if2

  br i1 %cmp.not, label %if.end11, label %if2

  %1 = load %p…
  br … %if.end11, %end



The PDOM tree looks like:
Inorder PostDominator Tree: DFSNumbers invalid: 0 slow queries.
  [1]  <<exit node>> {4294967295,4294967295} [0]
    [2] %end {4294967295,4294967295} [1]
      [3] %if2 {4294967295,4294967295} [2]     ; lower load block
      [3] %if.then {4294967295,4294967295} [2]  ; upper load block
      [3] %entry {4294967295,4294967295} [2]  ; null check for upper load
      [3] %if.end3 {4294967295,4294967295} [2]  ; null check for lower load
      [3] %if.end11 {4294967295,4294967295} [2]
Roots: %end

GVNHoist traverses the blocks in depth-first PDOM order. It hits the two load
blocks %if2 and %if.then, and pushes the loads on the stack, %1 and %0
respectively. When it processes the upper load-block %if.then, it correctly
places a chiarg (%if.then, %0) into its precedessor, %entry. %0 is popped off
the stack. The problem is that %1 remains at the top of the stack while it
traverses the other pdom siblings. When it gets to %if.end3, the other
successor of %entry, it places a chiarg (%if.end3, %1) into %entry, even though
%1 is not anticipable in %if.end3. It looks like the stacks should be popped
when we “backtrack” in the PDOM tree traversal, or maybe an extra pdom check
needs to be done before inserting a chiarg.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200728/d38224b1/attachment-0001.html>

More information about the llvm-bugs mailing list