From: Paolo Bonzini <bonzini@gnu.org>
To: Gregory Casamento <greg.casamento@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Incorporation of Objective-C 2.0 changes into GCC trunk
Date: Tue, 21 Jul 2009 19:50:00 -0000 [thread overview]
Message-ID: <4A661C02.6020401@gnu.org> (raw)
In-Reply-To: <8aefa2350907211247t7baa131fq8e99477ebc0fbbf7@mail.gmail.com>
Gregory Casamento wrote:
> All,
>
> Hey guys.... I'm wondering if there's a timeline for incorporating the
> Objective-C 2.0 changes from Apple into the trunk of GCC.
>
> If not, I would like to know what the GNUstep project can do to help
> make this happen.
No. But you just have to take patches from Apple's GCC, polish them and
send them.
Do Apple's changes rely on the NeXT runtime? If not, the job would be
easier.
Paolo
next prev parent reply other threads:[~2009-07-21 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 19:47 Gregory Casamento
2009-07-21 19:50 ` Paolo Bonzini [this message]
[not found] ` <0015175933a6e5738a046f3d1925@google.com>
2009-07-21 21:02 ` Gregory Casamento
2009-07-21 21:14 ` Paolo Bonzini
2009-07-22 8:57 ` Richard Guenther
2009-07-22 9:58 ` Paolo Bonzini
2009-07-22 16:26 ` Chris Lattner
2009-07-22 16:48 ` Paolo Bonzini
2009-07-22 11:06 ` Dave Korn
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=4A661C02.6020401@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=greg.casamento@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).