public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: William Schmidt <wschmidt@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 7eb81fbabc8ede30c1482f9452b1825d7fbd8c56 Date: Mon, 28 Sep 2020 17:02:26 +0000 (GMT) [thread overview] Message-ID: <20200928170226.2053D398641B@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 7eb81fbabc8ede30c1482f9452b1825d7fbd8c56 (commit) from 3f55a908204a438e7e1dfefd53892641b360066b (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 7eb81fbabc8ede30c1482f9452b1825d7fbd8c56 Author: Bill Schmidt <wschmidt@linux.ibm.com> Date: Mon Sep 28 12:02:01 2020 -0500 rs6000: Explain deprecated builtins more thoroughly I was contacted by a developer who was concerned about the deprecated builtins, until I explained their nature. As he suggested, I am adding more language here to avoid similar concerns from others. 2020-09-28 Bill Schmidt <wschmidt@linux.ibm.com> * htdocs/gcc-10/changes.html: Explain Power builtin deprecations. diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 4db307c7..759e4fd7 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -968,7 +968,13 @@ typedef svbool_t pred512 __attribute__((arm_sve_vector_bits(512))); <a href="https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture">64-Bit ELF V2 ABI Specification</a> for quite a number of years. The vector builtins listed in Tables A.8 through A.10 are now deprecated for GCC 10, and will likely be removed - from support in GCC 11. + from support in GCC 11. Note that this does not result in any loss of + function. These deprecated builtins generally provide somewhat + nonsensical argument lists (for example, mixing signed, unsigned, and + bool vector arguments arbitrarily), or are duplicate builtins that are + inconsistent with the expected naming scheme. We expect that this will + be unlikely to affect much if any code, and any required code changes + will be trivial. </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-09-28 17:02 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=20200928170226.2053D398641B@sourceware.org \ --to=wschmidt@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).