Displaying 5 results from an estimated 5 matches for "17160487".
Did you mean:
1716048f
2005 Mar 11
0
[LLVMdev] FP Intrinsics
...160465 fstp st(0)
17160467 jbe 17160498
1716046D mov eax,76E4F60h
17160472 mov dword ptr [esp+0Ch],eax
17160476 fld qword ptr [esp+14h]
1716047A fstp dword ptr [esp+8]
1716047E mov eax,15900060h
17160483 mov dword ptr [esp+4],eax
17160487 mov eax,161D6240h
1716048C mov dword ptr [esp],eax
1716048F call HueVMShaderCommands_LLVMShader1DLookupLinear
(19D8B76h)
17160494 add esp,1Ch
17160497 ret
17160498 mov dword ptr ds:[161D6240h],0
171604A2 mov dword ptr ds:[161D6244h],0
171604AC...
2005 Mar 11
5
[LLVMdev] FP Intrinsics
Hello,
I am trying to make the FP intrinsics (abs, sin, cos, sqrt) I've added
work with the X86ISelPattern, but I'm having some difficulties
understanding what needs to be done. I assume I have to add new
nodetypes for the FP instructions to SelectionDAGNodes.h, and make nodes
for these in SelectionDAGLowering::visitCall when I find the intrinsic...
The part I don't quite
2005 Mar 17
1
[LLVMdev] Floating point compare instruction selection
...60458 fnstsw ax
1716045A sahf
1716045B fldz
1716045D fchs
1716045F fld qword ptr [esp+14h]
17160463 fucomip st,st(1)
17160465 fstp st(0)
17160467 jbe 17160498
the ISelSimple generates:
1716047F call eax
17160481 fsub dword ptr ds:[16237240h]
17160487 fabs
17160489 fst qword ptr [esp+14h]
1716048D ftst
1716048F fstp st(0)
17160491 fnstsw ax
17160493 sahf
17160494 jbe 171604C7
m.
2005 Mar 16
0
[LLVMdev] Floating point compare instruction selection
On Wed, 16 Mar 2005, Morten Ofstad wrote:
> Hello,
>
> I didn't get any reply to my previous mail about adding floating point
> intrinsics to the X86 pattern instruction selector... And I could really need
> some help.
Sorry about that, it slipped through the cracks. :(
> Anyway, I think my confusion was caused partly by an already
> existing bug in the instruction
2005 Mar 16
2
[LLVMdev] Floating point compare instruction selection
Hello,
I didn't get any reply to my previous mail about adding floating point intrinsics to the X86 pattern instruction
selector... And I could really need some help. Anyway, I think my confusion was caused partly by an already existing bug
in the instruction selection for floating point compares.
The case which emits code for the special case of comparing against constant 0.0 does not