From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Cc: Iain Sandoe <developer@sandoe-acoustics.co.uk>,
Mike Stump <mikestump@comcast.net>
Subject: [wwwdocs] Objective-C/Darwin related updates for the GCC 4.6 release notes
Date: Mon, 07 Jan 2013 22:35:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1301061854160.15650@tuna.site> (raw)
Going through some older mails (as some may have noticed), I found
this patch which Iain was had done, and which I had reviewed, but
which somehow did not make it in.
Applied now, with some fuzzing manually adjusted.
Gerald
--- changes.html.orig 2012-10-03 07:02:42.198917592 -1000
+++ changes.html 2013-01-06 18:54:44.729487237 -1000
@@ -716,8 +716,7 @@
<li>As a result of these enhancements, GCC can now be used to
build Objective-C and Objective-C++ software that uses Foundation
and other important system frameworks with the NeXT runtime on
- Darwin 9 and Darwin 10 (Mac OS X 10.5 and 10.6). Currently this is for
- m32 code only.</li>
+ Darwin 9 and Darwin 10 (OSX 10.5 and 10.6).</li>
<li>Many bugs in the compiler have been fixed in this release; in
particular, LTO can now be used when compiling Objective-C and
@@ -1013,6 +1012,14 @@
allocators have been re-written to make more use of
<code>.zerofill</code> sections. For non-debug code, this can
reduce object file size significantly.</li>
+ <li>Objective-C family 64-bit support (NeXT ABI 2).<br />
+ Initial support has been added to support 64-bit Objective-C code
+ using the Darwin/OS X native (NeXT) runtime. ABI version 2 will be
+ selected automatically when 64-bit code is built.</li>
+ <li>Objective-C family 32-bit ABI 1.<br />
+ For 32-bit code ABI 1 is also now also allowed. At present it must
+ be selected manually using <code>-fobjc-abi-version=1</code> where
+ applicable - i.e. on Darwin 9/10 (OS X 10.5/10.6).</li>
</ul></li>
<li>x86 Architecture
<ul>
reply other threads:[~2013-01-07 22:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LNX.2.00.1301061854160.15650@tuna.site \
--to=gerald@pfeifer.com \
--cc=developer@sandoe-acoustics.co.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).