Displaying 2 results from an estimated 2 matches for "__fn_local_foovf".
2013 Apr 19
0
[LLVMdev] funny llvm bug
...ng code from gcc -mips16:
# Stub function for foovf (float)
.section .mips16.fn.foovf,"ax", at progbits
.align 2
.set nomips16
.set nomicromips
.ent __fn_stub_foovf
.type __fn_stub_foovf, @function
__fn_stub_foovf:
la $25,foovf
mfc1 $4,$f12
jr $25
.end __fn_stub_foovf
.text
$__fn_local_foovf = foovf
Not being sure about the restriction of section to just "name", well
docs can be wrong and not match the code, I Googled for this:
http://stackoverflow.com/questions/6252812/what-does-the-aw-flag-in-the-section-attribute-mean
This implied that it was okay to do what I tried....
2013 Apr 19
3
[LLVMdev] funny llvm bug
> It is exactly intended to handle section names as what they are --
> section names. The only reason it works with GCC is because it writes an
> assembler stream.
+1
Reed, this fails in gcc if you do LTO, no?
> Joerg
Cheers,
Rafael