public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-8789] c-family: Drop nothrow from c_keywords Date: Tue, 27 Sep 2022 14:41:53 +0000 (GMT) [thread overview] Message-ID: <20220927144153.A3EC13858403@sourceware.org> (raw) https://gcc.gnu.org/g:36c23b302c9487b34fa89daaf1a1a11514ce9bd2 commit r12-8789-g36c23b302c9487b34fa89daaf1a1a11514ce9bd2 Author: Marek Polacek <polacek@redhat.com> Date: Tue Sep 27 10:40:09 2022 -0400 c-family: Drop nothrow from c_keywords As discussed in <https://gcc.gnu.org/pipermail/gcc-patches/2022-September/602337.html>. gcc/c-family/ChangeLog: * c-format.cc (c_keywords): Drop nothrow. Diff: --- gcc/c-family/c-format.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/gcc/c-family/c-format.cc b/gcc/c-family/c-format.cc index ebdac57f943..d05e5acd063 100644 --- a/gcc/c-family/c-format.cc +++ b/gcc/c-family/c-format.cc @@ -2933,7 +2933,6 @@ static const token_t c_keywords[] = NAME ("noinline", NULL), NAME ("nonnull", NULL), NAME ("noreturn", NULL), - NAME ("nothrow", NULL), NAME ("offsetof", NULL), NAME ("readonly", "read-only"), NAME ("readwrite", "read-write"),
reply other threads:[~2022-09-27 14:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220927144153.A3EC13858403@sourceware.org \ --to=mpolacek@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).