This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] LTO support for Mach-O (apple-darwin)
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: Steven Bosscher <stevenb dot gcc at gmail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Mike Stump <mikestump at comcast dot net>, Richard Guenther <richard dot guenther at gmail dot com>, Diego Novillo <dnovillo at google dot com>, dave dot korn dot cygwin at googlemail dot com, Jack Howarth <howarth at nitro dot msbb dot uc dot edu>
- Date: Sun, 02 May 2010 15:34:34 +0100
- Subject: Re: [patch] LTO support for Mach-O (apple-darwin)
- References: <q2t571f6b511005020353o83872c45ydf898d748b164f05@mail.gmail.com>
On 02/05/2010 11:53, Steven Bosscher wrote:
> * lto-endian.h: New file.
This file begins with this comment:
> + enable cross-compilation with LTO enabled. Targets that use the
> + ELF binary object format do not need this (libelf already handles
> + endian-ness) but for COFF and Mach-O the functions in this header
> + are used in the minimal binary object reader/writer.
Except that's not correct w.r.t COFF, because you didn't go with your
original plan to share the common code, and you've renamed all the functions
so we can't simply change one #include, delete the definitions from
lto-coff.h, and have it "just work". Given that, I can't see the point in
making it a separate file anymore; doing so would just be introducing yet
another partial transition to no particular end, so why not just put the
contents in lto-macho.h instead?
cheers,
DaveK