2011-05-17 02:15:58 +02:00
|
|
|
; RUN: llc < %s -mtriple=x86_64-apple-macosx | FileCheck %s
|
MachineSink: Fix and tweak critical-edge breaking heuristic.
Per original comment, the intention of this loop
is to go ahead and break the critical edge
(in order to sink this instruction) if there's
reason to believe doing so might "unblock" the
sinking of additional instructions that define
registers used by this one. The idea is that if
we have a few instructions to sink "together"
breaking the edge might be worthwhile.
This commit makes a few small changes
to help better realize this goal:
First, modify the loop to ignore registers
defined by this instruction. We don't
sink definitions of physical registers,
and sinking an SSA definition isn't
going to unblock an upstream instruction.
Second, ignore uses of physical registers.
Instructions that define physical registers are
rejected for sinking, and so moving this one
won't enable moving any defining instructions.
As an added bonus, while virtual register
use-def chains are generally small due
to SSA goodness, iteration over the uses
and definitions (used by hasOneNonDBGUse)
for physical registers like EFLAGS
can be rather expensive in practice.
(This is the original reason for looking at this)
Finally, to keep things simple continue
to only consider this trick for registers that
have a single use (via hasOneNonDBGUse),
but to avoid spuriously breaking critical edges
only do so if the definition resides
in the same MBB and therefore this one directly
blocks it from being sunk as well.
If sinking them together is meant to be,
let the iterative nature of this pass
sink the definition into this block first.
Update tests to accomodate this change,
add new testcase where sinking avoids pipeline stalls.
llvm-svn: 192608
2013-10-14 18:57:17 +02:00
|
|
|
; This is supposed to be testing BranchFolding's common
|
|
|
|
|
; code hoisting logic, but has been erroneously passing due
|
|
|
|
|
; to there being a redundant xorl in the entry block
|
|
|
|
|
; and no common code to hoist.
|
|
|
|
|
; However, now that MachineSink sinks the redundant xor
|
|
|
|
|
; hoist-common looks at it and rejects it for hoisting,
|
|
|
|
|
; which causes this test to fail.
|
|
|
|
|
; Since it seems this test is broken, marking XFAIL for now
|
|
|
|
|
; until someone decides to remove it or fix what it tests.
|
|
|
|
|
; XFAIL: *
|
2011-05-12 22:30:01 +02:00
|
|
|
|
|
|
|
|
; Common "xorb al, al" instruction in the two successor blocks should be
|
|
|
|
|
; moved to the entry block above the test + je.
|
|
|
|
|
|
|
|
|
|
; rdar://9145558
|
|
|
|
|
|
|
|
|
|
define zeroext i1 @t(i32 %c) nounwind ssp {
|
|
|
|
|
entry:
|
2013-07-14 08:24:09 +02:00
|
|
|
; CHECK-LABEL: t:
|
2013-05-30 15:19:42 +02:00
|
|
|
; CHECK: xorl %eax, %eax
|
2011-05-12 22:30:01 +02:00
|
|
|
; CHECK: test
|
|
|
|
|
; CHECK: je
|
|
|
|
|
%tobool = icmp eq i32 %c, 0
|
|
|
|
|
br i1 %tobool, label %return, label %if.then
|
|
|
|
|
|
|
|
|
|
if.then:
|
|
|
|
|
; CHECK: callq
|
[opaque pointer type] Add textual IR support for explicit type parameter to the call instruction
See r230786 and r230794 for similar changes to gep and load
respectively.
Call is a bit different because it often doesn't have a single explicit
type - usually the type is deduced from the arguments, and just the
return type is explicit. In those cases there's no need to change the
IR.
When that's not the case, the IR usually contains the pointer type of
the first operand - but since typed pointers are going away, that
representation is insufficient so I'm just stripping the "pointerness"
of the explicit type away.
This does make the IR a bit weird - it /sort of/ reads like the type of
the first operand: "call void () %x(" but %x is actually of type "void
()*" and will eventually be just of type "ptr". But this seems not too
bad and I don't think it would benefit from repeating the type
("void (), void () * %x(" and then eventually "void (), ptr %x(") as has
been done with gep and load.
This also has a side benefit: since the explicit type is no longer a
pointer, there's no ambiguity between an explicit type and a function
that returns a function pointer. Previously this case needed an explicit
type (eg: a function returning a void() function was written as
"call void () () * @x(" rather than "call void () * @x(" because of the
ambiguity between a function returning a pointer to a void() function
and a function returning void).
No ambiguity means even function pointer return types can just be
written alone, without writing the whole function's type.
This leaves /only/ the varargs case where the explicit type is required.
Given the special type syntax in call instructions, the regex-fu used
for migration was a bit more involved in its own unique way (as every
one of these is) so here it is. Use it in conjunction with the apply.sh
script and associated find/xargs commands I've provided in rr230786 to
migrate your out of tree tests. Do let me know if any of this doesn't
cover your cases & we can iterate on a more general script/regexes to
help others with out of tree tests.
About 9 test cases couldn't be automatically migrated - half of those
were functions returning function pointers, where I just had to manually
delete the function argument types now that we didn't need an explicit
function type there. The other half were typedefs of function types used
in calls - just had to manually drop the * from those.
import fileinput
import sys
import re
pat = re.compile(r'((?:=|:|^|\s)call\s(?:[^@]*?))(\s*$|\s*(?:(?:\[\[[a-zA-Z0-9_]+\]\]|[@%](?:(")?[\\\?@a-zA-Z0-9_.]*?(?(3)"|)|{{.*}}))(?:\(|$)|undef|inttoptr|bitcast|null|asm).*$)')
addrspace_end = re.compile(r"addrspace\(\d+\)\s*\*$")
func_end = re.compile("(?:void.*|\)\s*)\*$")
def conv(match, line):
if not match or re.search(addrspace_end, match.group(1)) or not re.search(func_end, match.group(1)):
return line
return line[:match.start()] + match.group(1)[:match.group(1).rfind('*')].rstrip() + match.group(2) + line[match.end():]
for line in sys.stdin:
sys.stdout.write(conv(re.search(pat, line), line))
llvm-svn: 235145
2015-04-17 01:24:18 +02:00
|
|
|
%call = tail call zeroext i1 (...) @foo() nounwind
|
2011-05-12 22:30:01 +02:00
|
|
|
br label %return
|
|
|
|
|
|
|
|
|
|
return:
|
|
|
|
|
; CHECK: ret
|
|
|
|
|
%retval.0 = phi i1 [ %call, %if.then ], [ false, %entry ]
|
|
|
|
|
ret i1 %retval.0
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
declare zeroext i1 @foo(...)
|
