search for: e59d0004

...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: e8bd4800 pop {fp, lr} 8ba8: e12fff1e bx lr where the bl 0 causes a seg fault. I'll check x86_64, but currently don't have that setup, so it'll take me a little bit of...

...mp-def,dead>, %D26<imp-def,dead>, %D27<imp-def,dead>, %D28<imp-def,dead>, %D29<imp-def,dead>, %D30<imp-def,dead>, %D31<imp-def,dead>, %CPSR<imp-def,dead> 0xeb000000 JIT: 0x4512e028: %R0<def> = LDR %SP, %reg0, 4, 14, %reg0, Mem:LD(4,4) [b + 0] 0xe59d0004 JIT: 0x4512e02c: %R0<def> = ADDri %R0<kill>, 10, 14, %reg0, %reg0 0xe280000a JIT: 0x4512e030: %SP<def> = ADDri %SP<kill>, 8, 14, %reg0, %reg0 0xe28dd008 JIT: 0x4512e034: LDM_RET %SP, 9, 14, %reg0, %R11<def>, %PC<def> 0xe8bd8800 JIT: Map 'add1' to [0...

...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: e8bd4800 pop {fp, lr} > 8ba8: e12fff1e bx lr > > where the bl 0 causes a seg faul...

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