public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Marek Polacek <mpolacek@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 6c318f19e08bc7164fbee104a0d204cb26aca78b Date: Wed, 18 May 2022 23:25:40 +0000 (GMT) [thread overview] Message-ID: <20220518232540.77A5A3857360@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 6c318f19e08bc7164fbee104a0d204cb26aca78b (commit) from 8555f8647a4b5d86021e74e815b15ca98317c591 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 6c318f19e08bc7164fbee104a0d204cb26aca78b Author: Marek Polacek <polacek@redhat.com> Date: Wed May 18 19:25:15 2022 -0400 gcc-13/changes: Document -Wenum-int-mismatch diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index dc526530..969fb00b 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -56,6 +56,17 @@ a work-in-progress.</p> <!-- <h3 id="c-family">C family</h3> --> +<h3 id="c">C</h3> +<ul> + <li>New warnings: + <ul> + <li><code>-Wenum-int-mismatch</code> warns about mismatches between an + enumerated type and an integer type + (<a href="https://gcc.gnu.org/PR105131">PR105131</a>)</li> + </ul> + </li> +</ul> + <h3 id="cxx">C++</h3> <ul> <li>Several C++23 features have been implemented: ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 11 +++++++++++ 1 file changed, 11 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-05-18 23:25 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=20220518232540.77A5A3857360@sourceware.org \ --to=mpolacek@sourceware.org \ --cc=gcc-cvs-wwwdocs@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).