Displaying 3 results from an estimated 3 matches for "00008b88".
Did you mean:
000088b8
2014 May 30
3
[LLVMdev] Error with Gold Linker during LTO
So you see the issue as well in ARM? When doing a
objdump -D weakMainO1.exe | grep -A 10 "<_ZN1C13caller_methodEv>:"
I see:
00008b88 <_ZN1C13caller_methodEv>:
8b88: e92d4800 push {fp, lr}
8b8c: e1a0b00d mov fp, sp
8b90: e24dd008 sub sp, sp, #8
8b94: e58d0004 str r0, [sp, #4]
8b98: e59d0004 ldr r0, [sp, #4]
8b9c: ebffdd17 bl 0 <__preinit_array_end>
8ba0: e1a0d00b mov sp, fp
8ba4:...
2014 May 30
2
[LLVMdev] Error with Gold Linker during LTO
...ted program.
I can reproduce the issue now.
On 30 May 2014 15:48, Daniel Stewart <stewartd at codeaurora.org> wrote:
> So you see the issue as well in ARM? When doing a
>
> objdump -D weakMainO1.exe | grep -A 10 "<_ZN1C13caller_methodEv>:"
>
> I see:
>
> 00008b88 <_ZN1C13caller_methodEv>:
> 8b88: e92d4800 push {fp, lr}
> 8b8c: e1a0b00d mov fp, sp
> 8b90: e24dd008 sub sp, sp, #8
> 8b94: e58d0004 str r0, [sp, #4]
> 8b98: e59d0004 ldr r0...
2014 May 30
4
[LLVMdev] Error with Gold Linker during LTO
We've found an error during the use of LTO that appears to happen only
during the use of the gold linker.
We essentially have a file which is compiled *without* LTO:
f1() {
h1();
}
And a second file that is compiled/linked *with* LTO:
f2() {
f1();
h1();
}
This second file has the function h1() inlined during LTO.
The resulting executable fails because the symbol for h1