public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: Chris Lattner <clattner@apple.com>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: darwin LTO broken under Xcode 3.2.6/4.0
Date: Sun, 13 Mar 2011 20:03:00 -0000	[thread overview]
Message-ID: <20110313200334.GA13188@bromo.med.uc.edu> (raw)
In-Reply-To: <AANLkTikqBE5bi2iFOGEf8sumM5y3TCQ3oM13o2FxCZcq@mail.gmail.com>

On Sun, Mar 13, 2011 at 08:42:58PM +0100, Steven Bosscher wrote:
> (sorry Chris, I forgot the list)
> 
> On Mar 13, 2011,@11:59 AM, Chris Lattner wrote:
> 
> > Sorry, I actually mean 255 of course, because of the NO_SECT
> > sentinel.  Here are the relevant bits from nlist.h.  I'm not
> > sure how you expect the toolchain to store more than 256
> > sections in a uint8_t.
> 
> How self-righteous, and misinformed.
> 
> No-one is expecting to store >256 in a uint8_t. The structures you
> quote only apply to symbol tables, which are references into sections
> in Mach-O. But not all sections have symbols. None of the sections in
> the GNU_LTO segment have symbols.
> 
> The documentation you should be quoting is the part about Mach-O
> loader commands, and there is no limit AFAICT on the number of
> LC_SEGMENT/LC_SEGMENT_64 loader commands. There is also nothing in the
> segment command structures that suggests a limit of 255 sections.
> 
> Besides, it worked before, which suggests that, well, it worked.
> 
> This is not the limitation of Mach-O you are looking for.
> 
> Ciao!
> Steven

Steven,
   While I agree that we are likely correct in the details of this
problem, I suspect we will be unsuccessful in getting Apple to revert
this change. Even if they do so, it is likely to be for Xcode 4.0.1
only (since the 3.2.x series is being depreciated) and at best we
might see the fix in 6-9 months if not later. It is far better, despite
the pain, to recode this in order to protect ourselves in the future
from arbitary changes in Xcode. IMHO, one major problem is that Apple has
left mach-o poorly documented in some areas which leaves them the
lattitude to redefine the corner cases like this as they please.
                    Jack

  parent reply	other threads:[~2011-03-13 20:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-13 19:43 Steven Bosscher
2011-03-13 19:48 ` Chris Lattner
2011-03-13 20:03 ` Jack Howarth [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=20110313200334.GA13188@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=clattner@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=stevenb.gcc@gmail.com \
    /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).