public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 4755de58f65e3968a4bfcd1a1f34b8f635d5353e Date: Mon, 18 May 2020 19:14:02 +0000 (GMT) [thread overview] Message-ID: <20200518191402.51AD93851C05@sourceware.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2894 bytes --] 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 4755de58f65e3968a4bfcd1a1f34b8f635d5353e (commit) from c7b2066195cbfd33927c7b8fa571bf844fad9826 (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 4755de58f65e3968a4bfcd1a1f34b8f635d5353e Author: Jason Merrill <jason@redhat.com> Date: Mon May 18 15:09:25 2020 -0400 gcc-10/changes: Add -Warith-conversion. Also move Concepts to the top of the list. diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index abbafa58..fc58a471 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -275,6 +275,14 @@ You may also want to check out our out-of-bounds accesses by calls to user-defined functions declared with the new attribute <code>access</code>. </li> + <li><a href="https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Warning-Options.html#index-Warith-conversion"><code>-Warith-conversion</code></a> + re-enables warnings + from <code>-Wconversion</code>, <code>-Wfloat-conversion</code>, + and <code>-Wsign-conversion</code> that are now off by default for an + expression where the result of an arithmetic operation will not fit in + the target type due to promotion, but the operands of the expression do + fit in the target type. + </li> </ul> </li> <li>Extended characters in identifiers may now be specified directly in @@ -337,6 +345,7 @@ int get_naïve_pi() { <ul> <li>Several C++20 features have been implemented: <ul> + <li>Concepts, including P0734R0, P0857R0, P1084R2, P1141R2, P0848R3, P1616R1, P1452R2</li> <li>P1668R1, Permitting Unevaluated inline-assembly in constexpr Functions</li> <li>P1161R3, Deprecate <code>a[b,c]</code></li> <li>P0848R3, Conditionally Trivial Special Member Functions</li> @@ -345,7 +354,6 @@ int get_naïve_pi() { <li>P1152R4, Deprecating <code>volatile</code></li> <li>P0388R4, Permit conversions to arrays of unknown bound</li> <li>P0784R7, <code>constexpr new</code></li> - <li>Concepts, including P0734R0, P0857R0, P1084R2, P1141R2, P0848R3, P1616R1, P1452R2</li> <li>P1301R4, <code>[[nodiscard("with reason")]]</code></li> <li>P1814R0, class template argument deduction for alias templates</li> <li>P1816R0, class template argument deduction for aggregates</li> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-05-18 19:14 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=20200518191402.51AD93851C05@sourceware.org \ --to=jason@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).