From: Julian Waters <tanksherman27@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: [PING][PATCH v2] Add clang's invalid-noreturn warning flag
Date: Wed, 13 Sep 2023 11:09:41 +0800 [thread overview]
Message-ID: <CAP2b4GMfj0gX_AAHmu4xcNq2L6dOOHR8pFtZpYQ4MCcdzH-JEg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 98 bytes --]
Second desperate ping for patch
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627913.html
next reply other threads:[~2023-09-13 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 3:09 Julian Waters [this message]
2023-09-14 2:08 ` Julian Waters
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=CAP2b4GMfj0gX_AAHmu4xcNq2L6dOOHR8pFtZpYQ4MCcdzH-JEg@mail.gmail.com \
--to=tanksherman27@gmail.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).