From: Chris Lattner <clattner@apple.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc@gcc.gnu.org
Subject: Re: darwin LTO broken under Xcode 3.2.6/4.0
Date: Sun, 13 Mar 2011 18:55:00 -0000 [thread overview]
Message-ID: <0CEFDA0E-D81D-4EDD-8556-23D783B051C7@apple.com> (raw)
In-Reply-To: <20110313182611.GA12598@bromo.med.uc.edu>
On Mar 13, 2011, at 11:26 AM, Jack Howarth wrote:
>> Yes, I agree that this is a better solution. This error was put into the linker to detect some overflow conditions for part of the code that expected the section number to only be a byte. It is likely that "things worked" only out of luck before.
>>
>> -Chris
>
> Chris,
> Is there any documentation or example code on how to properly use subsections in mach-o?
> My fear is that we are moving from one poorly documented technique to another which may well
> have it own slate of hidden bugs.
I'm not sure what you mean here Jack. ld64 is open source on the darwin page, and if you have all the developer bits installed, the format is "documented" in /usr/include/mach-o/. It's pretty clear all around that you can only have 256 sections.
-Chris
next prev parent reply other threads:[~2011-03-13 18:55 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
2011-03-13 18:19 ` Chris Lattner
2011-03-13 18:26 ` Jack Howarth
2011-03-13 18:55 ` Chris Lattner [this message]
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=0CEFDA0E-D81D-4EDD-8556-23D783B051C7@apple.com \
--to=clattner@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.med.uc.edu \
--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).