public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63651] Lot of failures in obj(c|-c++) with yosemite
Date: Sat, 08 Nov 2014 14:22:00 -0000	[thread overview]
Message-ID: <bug-63651-4-gPZLDlEeV6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63651-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63651

--- Comment #7 from howarth at bromo dot med.uc.edu ---
(In reply to Iain Sandoe from comment #5)
> (In reply to Francois-Xavier Coudert from comment #4)
> > (In reply to Dominique d'Humieres from comment #3)
> > > Does it means that 'id' should be replaced with 'instancetype' in failing
> > > tests? What about the gnu-runtime?
> > 
> > No, we need to make the compiler understand 'instancetype'.
> 
> sadly, we spend almost all our darwin (volunteer) time chasing fall-out from
> other patches and very little remains for working on new features :-(
> 
> I'd love to modernise the ObjC stuff - bearing in mind that the biggest
> killer there is that we don't support blocks in GCC (ObjC is essentially not
> much usable on darwin >= 11, without that).
> 
> on the TODO ..

If I remember correctly, the blocks issue is problematic because of the blocks
runtime's license, so that whole package would have to be reverse engineered to
be under GPLv3, no?


  parent reply	other threads:[~2014-11-08 14:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-63651-4@http.gcc.gnu.org/bugzilla/>
2014-11-01 11:52 ` fxcoudert at gcc dot gnu.org
2014-11-07 23:02 ` fxcoudert at gcc dot gnu.org
2014-11-08 13:45 ` dominiq at lps dot ens.fr
2014-11-08 13:53 ` fxcoudert at gcc dot gnu.org
2014-11-08 14:07 ` iains at gcc dot gnu.org
2014-11-08 14:09 ` howarth at bromo dot med.uc.edu
2014-11-08 14:22 ` howarth at bromo dot med.uc.edu [this message]
2014-11-20 19:27 ` egall at gwmail dot gwu.edu
2014-11-20 19:47 ` howarth at bromo dot med.uc.edu
2014-12-20 10:54 ` dominiq at lps dot ens.fr
2014-12-20 12:44 ` dominiq at lps dot ens.fr
2014-12-20 16:12 ` fxcoudert at gcc dot gnu.org
2014-12-20 16:18 ` iains at gcc dot gnu.org
2014-12-22 10:18 ` iains at gcc dot gnu.org
2014-12-22 14:17 ` dominiq at lps dot ens.fr
2014-12-22 21:29 ` mrs at gcc dot gnu.org
2014-12-22 21:49 ` iains at gcc dot gnu.org

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=bug-63651-4-gPZLDlEeV6@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).