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: Wed, 26 Jun 2024 14:40:24 +0000 [thread overview]
Message-ID: <bug-78352-4-ZtV4Y5Fn7z@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 #31 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Sergey Fedorov from comment #29)
> (In reply to Eric Gallager from comment #25)
> > Cross-referencing against
> > https://github.com/apple/swift-corelibs-libdispatch/issues/765
>
> By the way, have you got some example code at hand which can serve as a
> test? It must not require C/C++ 2011, of course.
> I can try compiling it on 10.6 with its gcc.
Check any of the testcases in either of these directories starting with the
`block-` prefix:
https://github.com/apple-oss-distributions/gcc/tree/e19d86db70127e160b1c32557e0bb80ebc272f92/gcc/testsuite/g%2B%2B.apple
https://github.com/apple-oss-distributions/gcc/tree/e19d86db70127e160b1c32557e0bb80ebc272f92/gcc/testsuite/gcc.apple
(It's got to be from that particular commit, because that was the last release
before Apple stopped shipping the testsuite with their distribution of GCC)
prev parent reply other threads:[~2024-06-26 14:40 UTC|newest]
Thread overview: 21+ 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
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
2024-06-26 8:17 ` egallager at gcc dot gnu.org
2024-06-26 8:21 ` egallager at gcc dot gnu.org
2024-06-26 9:59 ` vital.had at gmail dot com
2024-06-26 13:49 ` vital.had at gmail dot com
2024-06-26 14:02 ` iains at gcc dot gnu.org
2024-06-26 14:40 ` egallager at gcc dot gnu.org [this message]
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-ZtV4Y5Fn7z@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).