search for: __call_stub_fp_fpff

Displaying 3 results from an estimated 3 matches for "__call_stub_fp_fpff".

2013 Apr 25
1
[LLVMdev] issues with InlineAsm class and #APP/#NOAPP
...include float, double, _Complex float and _Complex double. Parameter signatures of the form below need to be remapped: float double float, double float, float double, double double, float .section .mips16.call.fp.fpff,"ax", at progbits .align 2 .set nomips16 .set nomicromips .ent __call_stub_fp_fpff .type __call_stub_fp_fpff, @function __call_stub_fp_fpff: mtc1 $4,$f12 move $18,$31 jal fpff mfc1 $2,$f0 jr $18 .size __call_stub_fp_fpff, .-__call_stub_fp_fpff .end __call_stub_fp_fpff On 04/24/2013 04:25 PM, Rafael EspĂ­ndola wrote: >> We also wanted the stubs to be real functions...
2013 Apr 24
0
[LLVMdev] issues with InlineAsm class and #APP/#NOAPP
> We also wanted the stubs to be real functions to llvm. That allows them to > participate properly > in optimization of various levels (including LTO). They can even be inlined. > There are other > planned optimizations that would not work if they were not legitimate > functions. I am not saying that the functions should not exist in the IL, just that they should not be inline
2013 Apr 24
3
[LLVMdev] issues with InlineAsm class and #APP/#NOAPP
On 04/24/2013 03:47 PM, Rafael EspĂ­ndola wrote: > On 24 April 2013 18:30, reed kotler <rkotler at mips.com> wrote: >> There are a lot of issues. >> >> For one, the function I'm compiling is a mips16 function but the stubs being >> created are mips32 functions. >> > This looks similar to thumb x 32 bit arm. Wouldn't a similar solution > work for