Displaying 2 results from an estimated 2 matches for "xxx_extendsfdf2".
2013 Jan 20
2
[LLVMdev] soft float signature problem
...I have not fully examined
if it's all of them. So in callinfo while I'm lowering the call, the
first argument for example will appear to be a float.
For sure in the following situation:
float f;
...
printf("%f \n", f);
So it generates a libcall to widen f to double.
long int XXX_extendsfdf2(float);
The problem for me is that the parameter should be int since this is a
soft float routine. Probably nobody ever looks at this argument type in
this situation.
So I think this should look like:
long int XXX_extendsfdf2(int);
In my case the routine is called __mips16_extendsfdf2 .
When...
2013 Jan 22
0
[LLVMdev] soft float signature problem
What happens here is that the code that is doing the "softening",
generates a libcall
On closer inspection, llvm is doing half of this correctly.
The signature for the soft float function for extending a float to
double is of the form:
i64 xxx_extendsfdf2(float);
But it should be
i64 xxx_extendsfdf2(i32)
This particular paradigm is duplicated many times in the the float type
lowering.
I'm not sure exactly how to change this and what effect if any that it
might have.
thoughts?
In my case for mips16, it's important that I know the prop...