public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/78352] GCC lacks support for the Apple "blocks" extension to the C family of languages
Date: Sat, 07 Nov 2020 16:29:21 +0000	[thread overview]
Message-ID: <bug-78352-4-Fu0RBRImQl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-78352-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #12)
> (In reply to Fabian Groffen from comment #11)
> > Is there a patch or WIP somewhere I can try out or attempt to bring forwards?
> 
> I need to bring forward my patches to the latest master, will post a link
> here when that is done (it won't be soon - mainly because all time is being
> soaked up with work on the arm64 port for Apple Silicon). At present, I am
> also trying to resolve some of the other (smaller) objective-c issues
> preventing us from parsing the system headers.
> 
> > My attempts at porting the 4.2.1 Apple changes to 10.1 seem to have failed
> > as I get some weird "byref undeclared" errors whenever a __block var is
> > encountered.  I must admit I'm not really well versed with GCC's code.
> 
> The apple-4.2.1 branch is, indeed, too far removed from current trunk - and
> as far as I understand, we would not be permitted to apply those patches
> anyway, since they were not counted as contributed (not present on the FSF
> servers).  IANAL - but that's how I understand the rules.

If we could get in touch with an actual lawyer to review which laws
specifically are getting in the way here, that could be helpful. I won my
election to the New Hampshire State Legislature so if there's any legislation I
could pass to make it legal to apply those patches here in NH, I'd love to know
how to write it.

> 
> It would be great to have more than one person working on this - I will post
> here when the current WIP is published somewhere.

  parent reply	other threads:[~2020-11-07 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-78352-4@http.gcc.gnu.org/bugzilla/>
2020-11-07 12:36 ` grobian at gentoo dot org
2020-11-07 12:53 ` iains at gcc dot gnu.org
2020-11-07 16:29 ` egallager at gcc dot gnu.org [this message]
2020-11-08  9:11 ` grobian at gentoo dot org
2020-11-08  9:25 ` iains at gcc dot gnu.org
2020-11-09  8:20 ` redi at gcc dot gnu.org
2022-05-13 21:04 ` egor.pugin at gmail dot com
2022-11-05 19:23 ` vital.had at gmail dot com
2023-06-04 19:01 ` vital.had at gmail dot com
2023-06-04 19:28 ` iains at gcc dot gnu.org
2023-12-11 22:55 ` vital.had at gmail dot com
2023-12-11 22:58 ` pinskia at gcc dot gnu.org
2023-12-31  0:58 ` vital.had at gmail dot com
2023-12-31  7:24 ` iains at gcc dot gnu.org
2024-01-01  0:57 ` egallager 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-78352-4-Fu0RBRImQl@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).