2010/9/11 John E. / TDM <[email protected]>:
> On 9/11/2010 11:50 AM, Kai Tietz wrote:
>> Well, lto normally needs not to be explicit enabled. You just need to
>> have the libelf library installed on you host environment.
>
> Actually, libelf is not required to enable LTO for PE-COFF targets (i.e.
> Windows), since PE-COFF and ELF are two different formats. Due to the
> excellent work of Dave Korn, GCC has a built-in LTO translator for
> PE-COFF, and all you need is "--enable-lto" at configure time (see
> <http://gcc.gnu.org/ml/gcc-patches/2010-04/msg00612.html>).
>
> -John E. / TDM
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
Well, AFAIK (and I use libelf on cygwin) it works nice with libelf.
The issue is that LTO internally stores information in elf (within PE
coff sections). So I doubt what you are telling me, as my expirence
here tells me something else. Dave Korn ported the LTO backend for
COFF to encapsulate ELF into sections, but nevertheless libelf (which
isn't an elf OS specific library btw) is required so that LTO works as
it should.
Regards,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
