public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vital.had at gmail dot com" <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, 05 Nov 2022 19:23:34 +0000 [thread overview]
Message-ID: <bug-78352-4-r7sK6gd7eC@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
Sergey Fedorov <vital.had at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vital.had at gmail dot com
--- Comment #18 from Sergey Fedorov <vital.had at gmail dot com> ---
(In reply to Iain Sandoe from comment #15)
> Sorry that there hasn't been much progress on this - it *was* top of my
> GCC11 TODO list, and then Apple Si. came along and torpedoed that...
Any updates ever since? It seems that we need blocks to build libdispatch, and
we need libdispatch on PPC to build some useful stuff.
next prev parent reply other threads:[~2022-11-05 19:23 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
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 [this message]
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-r7sK6gd7eC@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).