public inbox for
help / color / mirror / Atom feed
From: Segher Boessenkool <>
Subject: gcc-wwwdocs branch master updated. f3c71720ba8ec2a5b44f038d0dd649037bffadf4
Date: Fri, 19 Nov 2021 21:43:31 +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  f3c71720ba8ec2a5b44f038d0dd649037bffadf4 (commit)
      from  dbaebcd450925b622572944dcb34b26b76466c26 (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 f3c71720ba8ec2a5b44f038d0dd649037bffadf4
Author: Segher Boessenkool <>
Date:   Fri Nov 19 21:41:58 2021 +0000

    git: Add devel/power-ieee128 architecture-specific branch

diff --git a/htdocs/git.html b/htdocs/git.html
index 881f1d38..de8f0584 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -301,11 +301,13 @@ in Git.</p>
 <h4 id="arch">Architecture-specific</h4>
-<p>No active branches</p>
+  <dt>power-ieee128</dt>
+  <dd>This branch is for community development of IEEE quad precision floating
+      point for Power ("ieee128"), replacing the "double double" aka "ibm128"
+      implementation we had for long double.  The current focus is on Fortran
+      support.</dd>
 <h4 id="target">Target-specific</h4>


Summary of changes:
 htdocs/git.html | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)


                 reply	other threads:[~2021-11-19 21:43 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).