public inbox for
help / color / mirror / Atom feed
From: William Schmidt <>
Subject: gcc-wwwdocs branch master updated. e8cffe6d8fa529066a3e012599f9f417ddf0e855
Date: Tue, 23 Nov 2021 17:05:49 +0000 (GMT)	[thread overview]
Message-ID: <> (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  e8cffe6d8fa529066a3e012599f9f417ddf0e855 (commit)
      from  535e392dde5954ea7c40dd88952d775f38b74000 (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 e8cffe6d8fa529066a3e012599f9f417ddf0e855
Author: Bill Schmidt <>
Date:   Tue Nov 23 11:05:03 2021 -0600

    rs6000: Add information about built-ins to GCC 12 release notes

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 2f80b34a..89cbbdd8 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -294,7 +294,27 @@ a work-in-progress.</p>
 <!-- <h3 id="hppa">PA-RISC</h3> -->
-<!-- <h3 id="powerpc">PowerPC / PowerPC64 / RS6000</h3> -->
+<h3 id="powerpc">PowerPC / PowerPC64 / RS6000</h3>
+  <li>
+    The internal implementation of Power's target-specific built-in functions
+    has been rewritten to be easier and less error-prone to maintain.  Every
+    attempt has been made to ensure that the new behavior matches the old
+    behavior, but inevitably some bugs can be expected.  Please report any
+    problems using <a href="">GCC Bugzilla</a>.
+  </li>
+  <li>
+    The built-in functions <code>__builtin_get_texasr</code>,
+    <code>__builtin_get_texasru</code>, <code>__builtin_get_tfhar</code>,
+    <code>__builtin_get_tfiar</code>, <code>__builtin_set_texasr</code>,
+    <code>__builtin_set_texasru</code>, <code>__builtin_set_tfhar</code>, and
+    <code>__builtin_set_tfiar</code> now behave as documented in all
+    supported configurations.  On prior releases, the arguments and return
+    values of these functions were treated as <code>unsigned long long</code>
+    instead of as <code>unsigned long</code>, when the options <code>-m32
+    -mpowerpc64</code> were in effect.
+  </li>
 <h3 id="pru">PRU</h3>


Summary of changes:
 htdocs/gcc-12/changes.html | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)


                 reply	other threads:[~2021-11-23 17:05 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be 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).