Displaying 8 results from an estimated 8 matches for "ftoi".
Did you mean:
atoi
2016 Apr 27
2
[Sparc] builtin setjmp / longjmp - need help to get past last problem
...turn "SPISD::SELECT_ICC";
! case SPISD::SELECT_XCC: return "SPISD::SELECT_XCC";
! case SPISD::SELECT_FCC: return "SPISD::SELECT_FCC";
! case SPISD::Hi: return "SPISD::Hi";
! case SPISD::Lo: return "SPISD::Lo";
! case SPISD::FTOI: return "SPISD::FTOI";
! case SPISD::ITOF: return "SPISD::ITOF";
! case SPISD::FTOX: return "SPISD::FTOX";
! case SPISD::XTOF: return "SPISD::XTOF";
! case SPISD::CALL: return "SPISD::CALL";
! case SPISD::RET_...
2002 Mar 05
1
ogg vorbis on the pocket pc
...rks, so
i hope this is within the topic of the list, but i didnt really want to
leave this thing i've did out in the dark either. :)
i've just ported libvorbis, libogg, and vorbisfile stuff to the pocket pc
a while ago, it was pretty straight forward (just add a few more #ifdefs
around the ftoi function and some others) and written a player for it.
it can be found at http://www.dot9.ca/~cyanphase/pocketogg/
(i havent seen anyone else doing this before so i hope i'm not repeating
anything already).
i kind of stuck all 3 libs into 1 tho, i guess i was lazy, i'll fix that
soon.
i...
2012 Jul 26
3
[LLVMdev] proposal for exploiting undefined behavior much more aggressively
http://blog.regehr.org/archives/761
Thanks,
John
2012 Jul 26
0
[LLVMdev] proposal for exploiting undefined behavior much more aggressively
...for the project to be actively hostile to users of the compiler. :) It is useful to have debugging tools for people who really care, but "exploiting" undefined behavior just for the sake of breaking code is a non-goal.
A specific example is code like this (which is quite common):
int ftoi(float F) {
return *(int*)&F;
}
This is a violation of the C spec, due to type-based aliasing issues (the right approach is to use a union). That said, we go out of our way to not break this sort of idiom, because it is obvious to the compiler and actively hostile to a widely used pattern in...
2008 Oct 07
0
[LLVMdev] Multi instruction pattern help
On Oct 7, 2008, at 9:30 AM, Villmow, Micah wrote:
> Chris,
> Thanks for the help, this will help me with writing more patterns,
> but I am still hitting another roadblock. I attempted what you
> suggested and it fixed that issue, but then it started giving a
> warning that there is an unknown node in the resulting pattern.
>
> // unsigned int: f64->i32 ==>
2008 Oct 07
3
[LLVMdev] Multi instruction pattern help
Chris,
Thanks for the help, this will help me with writing more patterns, but
I am still hitting another roadblock. I attempted what you suggested and
it fixed that issue, but then it started giving a warning that there is
an unknown node in the resulting pattern.
// unsigned int: f64->i32 ==> f64->f32 + f32->i32
def : Pat<(i32 (fp_to_uint (f64 GPR:$src0))),
(i32
2010 Oct 15
0
Wine release 1.3.5
...ce7_Blt().
wined3d: Recognize the SM4 sampler register type.
wined3d: Recognize the SM4 resource register type.
wined3d: Skip SM4 source register modifiers.
wined3d: Skip SM4 instruction modifiers.
wined3d: Recognize the SM4 div opcode.
wined3d: Recognize the SM4 ftoi opcode.
wined3d: Recognize the SM4 ieq opcode.
wined3d: Recognize the SM4 ld opcode.
wined3d: Recognize the SM4 ABS and NEG source modifiers.
wined3d: Recognize the SM4 sample_d opcode.
d3d10core: Implement device_parent_CreateVolume().
d3d10core: Rename texture2...
2012 Jul 16
3
[LLVMdev] RFC: LLVM incubation, or requirements for committing new backends
...nOp = ISD::FP_TO_SINT;
> + } else {
> + // I don't think there will be any other type pairings.
> + assert(!"Unhandled operand type parings in SELECT_CC");
> + }
> + // XXX Check the value of LHS and RHS and avoid creating sequences like
> + // (FTOI (ITOF))
> + LHS = DAG.getNode(ConversionOp, DL, VT, LHS);
> + RHS = DAG.getNode(ConversionOp, DL, VT, RHS);
> + }
> +
> + // If True is a hardware TRUE value and False is a hardware FALSE value or
> + // vice-versa we can handle this with a native instruction (SET* instru...