From: Kaz Kylheku <kaz@kylheku.com>
To: gcc-patches@gcc.gnu.org
Subject: [April 2022 PING] cpp: new built-in __EXP_COUNTER__
Date: Mon, 28 Aug 2023 10:09:29 -0700 [thread overview]
Message-ID: <4d4c1b87a99944e8de160fe35ed9a9d0@kylheku.com> (raw)
In-Reply-To: <e51ca6b610b93a4d6d2158ce272c1b12@kylheku.com>
On 2022-06-13 16:13, Kaz Kylheku wrote:
> Pinging this item:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593473.html
>
> Thanks.
next prev parent reply other threads:[~2023-08-28 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 16:11 [PATCH v2] " Kaz Kylheku
2022-05-04 20:58 ` Kaz Kylheku
2022-05-14 15:44 ` [PING] " Kaz Kylheku
2022-06-13 23:13 ` Kaz Kylheku
2023-08-28 17:09 ` Kaz Kylheku [this message]
2024-02-10 20:50 ` [April 2022 PING] " Kaz Kylheku
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=4d4c1b87a99944e8de160fe35ed9a9d0@kylheku.com \
--to=kaz@kylheku.com \
--cc=gcc-patches@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).