Displaying 3 results from an estimated 3 matches for "bxlt".
Did you mean:
bolt
2010 Oct 08
0
[LLVMdev] Flag output used by two other nodes in DAG
Hello, Edmund,
> Is it, or should it be legal for a Flag output to be used as input by
> more than one other node?
It's illegal. Multiple uses of the flag output do not make any sense,
this breaks the semantics of flag operands.
--
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University
2010 Oct 08
1
[LLVMdev] Flag output used by two other nodes in DAG
...g value generated by one instruction is to be used as input to two other
instructions?
For a concrete example, consider:
int f(int x)
{
return x < 0 ? 11 : x == 0 ? 22 : 33;
}
I'd like this to turn into something like what I've seen from other compilers:
cmp r0, #0
movlt r0, #11
bxlt lr
movne r0, #33
moveq r0, #22
bx lr
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any...
2010 Oct 08
2
[LLVMdev] Flag output used by two other nodes in DAG
I recently filed this bug: http://llvm.org/bugs/show_bug.cgi?id=8323
It's a dodgy one because you have to patch LLVM to demonstrate it.
I suspect that the cause of the problem in that "bug" is that the
peephole optimisation in PerformDAGCombine results in a Flag output
from one node being used as input by two other nodes in the DAG, and
the scheduler then can't cope with that.