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. c2db1d56d28f04ba1b023d6f5d48d7948e9079d8 Date: Thu, 24 Feb 2022 16:12:21 +0000 (GMT) [thread overview] Message-ID: <20220224161221.AADEE3858402@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 c2db1d56d28f04ba1b023d6f5d48d7948e9079d8 (commit) from 5b042fc356bc84a79bd86fed4f99796b9638f809 (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 c2db1d56d28f04ba1b023d6f5d48d7948e9079d8 Author: Bill Schmidt <wschmidt@linux.ibm.com> Date: Thu Feb 24 10:11:48 2022 -0600 powerpc: Document vec_cnt[lt]z_lsbb semantics change diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index b6341fda..4be3ee72 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -442,6 +442,11 @@ a work-in-progress.</p> instead of as <code>unsigned long</code>, when the options <code>-m32 -mpowerpc64</code> were in effect. </li> + <li> + The overloaded built-in functions <code>vec_cntlz_lsbb</code> and + <code>vec_cnttz_lsbb</code> now behave as documented. On prior releases, + these built-in functions had incorrect semantics on little-endian targets. + </li> </ul> <h3 id="pru">PRU</h3> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 5 +++++ 1 file changed, 5 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-02-24 16:12 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=20220224161221.AADEE3858402@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).