Displaying 6 results from an estimated 6 matches for "iflt".
Did you mean:
flt
2004 Jun 09
2
[LLVMdev] BranchInst problem
...<fi#-2>
> > setcc %reg1024, %reg1025
> > goto %disp(label then)
> > goto %disp(label else)
>
> I assume that the two unconditional gotos are just test code, right? If
> not, the second one is dead.
Yes, in the final form there will be "iflt" instruction before the first goto,
making it conditional.
> > The code after "goto" is disturbing. It looks like spill code, but it's
> > not going to be ever executed. Any ideas why it's generated? Is there any
> > additional information I should provide...
2004 Jun 08
0
[LLVMdev] BranchInst problem
On Tue, 8 Jun 2004, Vladimir Prus wrote:
> While adding support for branch instructions in my backend, I run into a
> trouble. The code to handle branches looks like:
> The machine code after instruction selection is:
>
> entry (0x8681458):
> %reg1024 = load <fi#-1>
> %reg1025 = load <fi#-2>
> setcc %reg1024, %reg1025
>
2004 Jun 09
0
[LLVMdev] BranchInst problem
On Wed, 9 Jun 2004, Vladimir Prus wrote:
> > I assume that the two unconditional gotos are just test code, right? If
> > not, the second one is dead.
>
> Yes, in the final form there will be "iflt" instruction before the first goto,
> making it conditional.
Ah, ok :)
> > > The code after "goto" is disturbing. It looks like spill code, but it's
> > > not going to be ever executed. Any ideas why it's generated? Is there any
> > > additiona...
2004 Jun 08
2
[LLVMdev] BranchInst problem
While adding support for branch instructions in my backend, I run into a
trouble. The code to handle branches looks like:
void visitBranchInst(BranchInst& BI)
{
BB->addSuccessor (MBBMap[BI.getSuccessor(0)]);
if (BI.isConditional())
BB->addSuccessor (MBBMap[BI.getSuccessor(1)]);
...........
BuildMI(BB,
2016 Nov 26
3
ifelse() woes ... can we agree on a ifelse2() ?
...mals(FUN))[[4]] != "NA.") {
? ? ? ? ? ? body(FUN) <- do.call(substitute, list(body(FUN),
? ? ? ? ? ? ? ? setNames(list(quote(NA.)), names(formals(FUN))[[4]])))
? ? ? ? ? ? names(formals(FUN))[[4]] <- "NA."
? ? ? ? }
After fixing, chkIfelse(ifelseHW) just fails at identical(iflt, as.POSIXlt(ifct)) .
'iflt' has NA as 'tzone' and 'isdst' components.
* Because function 'chkIfelse' continues checking after failure,
as.POSIXlt(ifct)
may give error. The error happens, for example, in chkIfelse(ifelseR) . Maybe place it inside try(...).
* If 'l...
2016 Nov 28
0
ifelse() woes ... can we agree on a ifelse2() ?
...list(body(FUN),
> ? ? ? ? ? ? ? ? setNames(list(quote(NA.)), names(formals(FUN))[[4]])))
> ? ? ? ? ? ? names(formals(FUN))[[4]] <- "NA."
> ? ? ? ? }
yes, thank you! (a bit embarrassing for me ..)
> After fixing, chkIfelse(ifelseHW) just fails at identical(iflt, as.POSIXlt(ifct)) .
> 'iflt' has NA as 'tzone' and 'isdst' components.
> * Because function 'chkIfelse' continues checking after failure,
> as.POSIXlt(ifct)
> may give error. The error happens, for example, in chkIfelse(ifelseR) . Maybe p...