[LLVMdev] Mach-O LTO and local relocations

[Devang Patel]

On Thu, Apr 29, 2010 at 6:19 AM, Jack Howarth <howarth at bromo.med.uc.edu> wrote:

> When the assembly files are modified by hand, it has been found that
> if the normal output of -flto in FSF gcc is changed from...
>
> LTO sections (the __GNU_LTO stuff)
> .text / .data / etc. (all non-LTO sections)
> LTO __section_names section
>
> ...to a re-ordered .s file of...
>
> .text / .data / etc. (all non-LTO sections)
> LTO sections (the __GNU_LTO stuff)
> LTO __section_names section
>
> ...the linker error disappears. I am asking here because it is unclear
> how much of the Mach-O handling routines in clang were 'borrowed'
> from gcc 4.2.1 such that a fix to this issue may already be present
> in the llvm/clang.

Note, llvm LTO does not use separate LTO sections.
-
Devang