Displaying 12 results from an estimated 12 matches for "cond_false".
2014 Mar 03
6
[Bug 2207] New: Potential NULL deference, found using coverity
...ot;, __func__);
283 goto out;
284 }
'!strcmp(kdfname, "none") && !strcmp(kdfname, "bcrypt")' can never be
true.
(I appologize that line numbers are offset by -3.)
Error: FORWARD_NULL:
path:/c/amesh/142/src/crypto/openssh/authfile.c:224:
cond_false: Condition "len < m1len", taking false branch
path:/c/amesh/142/src/crypto/openssh/authfile.c:224:
cond_false: Condition "memcmp(cp, "-----BEGIN OPENSSH PRIVATE
KEY-----\n", m1len)", taking false branch
path:/c/amesh/142/src/crypto/openssh/authfile.c:227:
if_end: En...
2011 Aug 31
2
[LLVMdev] How to place call(s) to functions found in other llvm modules ???
...dominate all uses!
%tmp = call i32 @gcd(i32 30, i32 50)
ret i32 %tmp
Broken module found, verification continues.
Broken module found, verification continues.
; ModuleID = 'GCD'
define i32 @gcd(i32 %x, i32 %y) {
entry:
%tmp = icmp eq i32 %x, %y
br i1 %tmp, label %return, label %cond_false
return: ; preds = %entry
ret i32 %x
cond_false: ; preds = %entry
%tmp2 = icmp ult i32 %x, %y
br i1 %tmp2, label %cond_true, label %cond_false1
cond_true: ; preds = %con...
2017 Feb 05
3
Adding Extended-SSA to LLVM
...the future will).
>
It's important to note: we sort phi node uses into the predecessor block
they belong to, so that restriction does *not* apply to the typical phi
node use case.
IE given:
define i32 @test12(i32 %x) {
%cmp = icmp eq i32 %x, 0
br i1 %cmp, label %cond_true, label %cond_false
cond_true:
br label %ret
cond_false:
br label %ret
ret:
%res = phi i32 [ %x, %cond_true ], [ %x, %cond_false ]
ret i32 %res
}
You will get:
; CHECK-LABEL: @test12(
; CHECK-NEXT: [[CMP:%.*]] = icmp eq i32 [[X:%.*]], 0
; CHECK-NEXT: br i1 [[CMP]], label [[COND_TRUE:%.*]]...
2007 Aug 02
0
[LLVMdev] Debug info for conditionally defined variables?
....dbg.variable.type* @llvm.dbg.variable792014 to { }*) )
// Declares tm as tm
call void @llvm.dbg.declare( { }* %tm8, { }* bitcast
(%llvm.dbg.variable.type* @llvm.dbg.variable91 to { }*) )
...
cond_true:
%tmp15 = call %struct.tm* @localtime( i64* %curr )
br label %cond_next
cond_false:
%tmp16 = call %struct.tm* @gmtime( i64* %curr )
br label %cond_next
cond_next:
%storemerge = phi %struct.tm* [ %tmp15, %cond_true ], [ %tmp16,
%cond_false ]
store %struct.tm* %storemerge, %struct.tm** %iftmp.0
%tmp17 = load %struct.tm** %iftmp.0
store %struct.tm* %tmp17, %...
2007 Jul 02
1
[LLVMdev] Getting the target information of a branch instruction
......
for that i am checking if the opcode is terminator and after that i am
getting the opcode name and if it is a branch instruction then i should
get the statement number of the branch...i am using a map to associate an
instruction with number...i had a look at the IR and it has inserted
cond_true,cond_false and cond_next labels in the IR of the bytecode...
How do i go further with these values in hand?
please guide on this topic.
Thanks a lot.
abhinav.
2007 Jul 02
2
[LLVMdev] Getting the target information of a branch instruction
...m checking if the opcode is terminator and after that i am
>getting the opcode name and if it is a branch instruction then i should
>get the statement number of the branch...i am using a map to associate an
>instruction with number...i had a look at the IR and it has inserted
>cond_true,cond_false and cond_next labels in the IR of the bytecode...
>
>How do i go further with these values in hand?
>please guide on this topic.
>Thanks a lot.
>abhinav.
>_______________________________________________
>LLVM Developers mailing list
>LLVMdev at cs.uiuc.edu http://llv...
2007 Jul 12
1
[LLVMdev] backend problem with LiveInterval::removeRange
...30, 0x88c8d70, 0x88c8dd8
0x88c94d8: i1 = Constant <0>
0x88c8fc8: <multiple use>
0x88c8fc8: <multiple use>
0x88c9060: i32 = Constant <2>
0x88c9360: ch = setne
0x88c89a8: i1 = setcc 0x88c8fc8, 0x88c9060, 0x88c9360
0x88c9540: ch = BasicBlock <cond_false 0x88c7db8>
0x88c95a8: ch = brcond 0x88c8fc8:1, 0x88c89a8, 0x88c9540
Legalized selection DAG:
SelectionDAG has 16 nodes:
0x88c88a0: ch = EntryToken
0x88c8d70: i32 = FrameIndex <0>
0x88c8dd8: i32 = undef
0x88c88a0: <multiple use>
0x88c88a0: <multiple use...
2017 Feb 02
4
Adding Extended-SSA to LLVM
Hey folks,
After a long amount of discussion both offline and on, I put a
pass/intrinsic to add extended SSA up at http://reviews.llvm.org/D29316.
Sean asked me to share it more broadly on llvm-dev, so here you go :)
For those not familiar with extended-SSA, it's described in the paper
"ABCD: Eliminating Array Bounds Checks on Demand".
There is a very large amount of explanation
2007 Jul 02
0
[LLVMdev] Getting the target information of a branch instruction
...e opcode is terminator and after that i am
>>getting the opcode name and if it is a branch instruction then i should
>>get the statement number of the branch...i am using a map to associate an
>>instruction with number...i had a look at the IR and it has inserted
>>cond_true,cond_false and cond_next labels in the IR of the bytecode...
>>
>>How do i go further with these values in hand?
>>please guide on this topic.
>>Thanks a lot.
>>abhinav.
>>_______________________________________________
>>LLVM Developers mailing list
>>LLVMdev a...
2007 Jul 02
0
[LLVMdev] Getting the target information of a branch instruction
On Mon, 2 Jul 2007 abhi232 at cc.gatech.edu wrote:
> Hello all,
> I am new to the llvm infrastructure so if this question is already
> resolved please redirect me to that link.
>
> I am writing a pass for flow sensitive and context sensitive alias
> analysis.for that i require the previous and next instruction of all the
> instructions.Is there an intrinsic that can help me
2007 Jul 02
2
[LLVMdev] Getting the target information of a branch instruction
Hello all,
I am new to the llvm infrastructure so if this question is already
resolved please redirect me to that link.
I am writing a pass for flow sensitive and context sensitive alias
analysis.for that i require the previous and next instruction of all the
instructions.Is there an intrinsic that can help me getting the
instruction numbers directly because i read at the llvm.org website making
2008 Jan 12
1
[LLVMdev] Labels
...mp16 = sub i32 %tmp14, %tmp12
store i32 %tmp16, i32* @yyend, align 4
store i32 0, i32* @yythunkpos, align 4
store i32 0, i32* @yypos, align 4
ret void
}
declare void @llvm.memmove.i32(i8*, i8*, i32, i32)
define i32 @yyAccept(i32 %tp0)
{
entry:
%tmp2 = icmp eq i32 %tp0, 0
br i1 %tmp2, label %cond_false, label %UnifiedReturnBlock
cond_false:
tail call void @yyDone( )
tail call void @yyCommit( )
ret i32 1
UnifiedReturnBlock:
ret i32 0
}
define void @yyPush(i8* %text, i32 %count)
{
entry:
%tmp = load i32** @yyval, align 4
%tmp2 = getelementptr i32* %tmp, i32 %count
store i32* %tmp2, i32**...