From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc@gcc.gnu.org
Subject: Re: darwin LTO broken under Xcode 3.2.6/4.0
Date: Sun, 13 Mar 2011 15:38:00 -0000 [thread overview]
Message-ID: <20110313153841.GA11318@bromo.med.uc.edu> (raw)
In-Reply-To: <20110313113926.GP12469@atrey.karlin.mff.cuni.cz>
On Sun, Mar 13, 2011 at 12:39:26PM +0100, Jan Hubicka wrote:
> > With release of Xcode 3.2.6/4.0 this week, an unfortunate change was made to
> > the darwin assembler which effectively breaks LTO support for darwin. The design
> > of LTO on darwin was based on the fact that mach-o object files tolerated additional
> > sections as long as they didin't contain symbols. With Xcode 3.2.6/4.0, the assembler
> > appears to be strictly counting sections and objecting when these exceed 255. This
> > breaks huge sections of the lto testsuite and prevents larger projects like xplor-nih
> > to compile if Xcode 3.2.6/4.0 is installed. I am afraid that unless Apple reverts this
> > change, our only recourse would be to resort to an elf object container for the lto
> > sections within the mach-o files (introducing an undesired dependency on libelf for
> > FSF gcc on darwin). My understanding was that the lto design did not allow the number
> > of sections required in the lto files to be reduced.
>
> If the problem is not fixed, we could always pack all the LTO sections into one section containing
> our own subsections.
>
> Honza
Jan,
If this could be done without resorting to other container types (like elf), it might be
the wisest approach for the long run. I've read through the mach-o documentation and it
seems rather vague on the section limits. Even if Apple fixes Xcode (which likley won't
happen for 6-9 months at best), we always we have to worry that they will break this
'feature' somewhere else in their tool chain. Better to follow the strictest possible reading
of mach-o object format to protect ourselves from overzealous Apple interns.
> > Jack
next prev parent reply other threads:[~2011-03-13 15:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 4:17 Jack Howarth
2011-03-13 7:35 ` Ian Lance Taylor
2011-03-13 7:52 ` Chris Lattner
2011-03-13 7:52 ` Jack Howarth
2011-03-13 11:39 ` Jan Hubicka
2011-03-13 15:38 ` Jack Howarth [this message]
2011-03-13 18:19 ` Chris Lattner
2011-03-13 18:26 ` Jack Howarth
2011-03-13 18:55 ` Chris Lattner
2011-03-13 18:59 ` Chris Lattner
2011-03-13 19:11 ` Jack Howarth
2011-03-13 19:05 ` Jack Howarth
2011-03-13 19:47 ` Chris Lattner
2011-03-13 19:56 ` Jack Howarth
2011-03-13 20:43 ` Jack Howarth
2011-03-13 19:07 ` Jan Hubicka
2011-03-13 19:45 ` Chris Lattner
2011-03-13 18:35 ` Jack Howarth
2011-03-13 18:54 ` Ian Lance Taylor
2011-03-14 19:48 ` Jack Howarth
2011-03-14 21:09 ` Ian Lance Taylor
2011-03-14 21:33 ` Jack Howarth
2011-03-13 19:43 Steven Bosscher
2011-03-13 19:48 ` Chris Lattner
2011-03-13 20:03 ` Jack Howarth
2011-03-13 20:38 ` Steven Bosscher
2011-03-13 20:41 ` Jack Howarth
2011-03-13 20:43 ` Steven Bosscher
2011-03-13 20:49 ` Jack Howarth
2011-03-13 20:55 ` Jack Howarth
2011-03-13 21:13 ` Jack Howarth
2011-03-14 17:20 ` Jack Howarth
2011-04-02 22:27 ` Gerald Pfeifer
2011-03-13 23:03 ` Jack Howarth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110313153841.GA11318@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).