public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 081a380b5e869dfb38bd2cda860d1400296df286 Date: Tue, 15 Sep 2020 15:35:00 +0000 (GMT) [thread overview] Message-ID: <20200915153500.131DF3861878@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 081a380b5e869dfb38bd2cda860d1400296df286 (commit) from 2f6aed80eb795f66a26cab2b5eee598d68f76ae5 (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 081a380b5e869dfb38bd2cda860d1400296df286 Author: Jeff Law <law@redhat.com> Date: Tue Sep 15 09:34:40 2020 -0600 Notes on ordered comparisons, dynamic exceptions and comparison objects diff --git a/htdocs/gcc-11/porting_to.html b/htdocs/gcc-11/porting_to.html index 5db00734..ee7e91d8 100644 --- a/htdocs/gcc-11/porting_to.html +++ b/htdocs/gcc-11/porting_to.html @@ -66,6 +66,22 @@ than the other, so it's ambiguous.</p> <p>The new behavior can be disabled independently of other C++17 features with <code>-fno-new-ttp-matching</code>.</p> +<h3 id="Ordered pointer comparison with integer">Ordered pointer comparison with integer</h3> +<p> +GCC 11 now issues a diagnostic for ordered comparisons of pointers against constant +integers. Commonly this is an ordered comparison against NULL or 0. These should be +equality comparisons, not ordered comparisons. +</p> + +<h3 id="Dynamic Exception Specifications</h3> +<p> +GCC 11 defaults to C++17 which does not allow dynamic exception specifications. +</p> + +<h3 id="Comparison Functions</h3> +<p> +GCC 11 now enforces that comparison objects be invocable as const. + <!-- <h2 id="fortran">Fortran language issues</h2> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-11/porting_to.html | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-09-15 15:35 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=20200915153500.131DF3861878@sourceware.org \ --to=law@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).