public inbox for
help / color / mirror / Atom feed
From: Thomas König <>
Subject: gcc-wwwdocs branch master updated. 6242231510406a9bc0b8cca3a06afab352ff48f7
Date: Sat, 30 Apr 2022 21:55:08 +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  6242231510406a9bc0b8cca3a06afab352ff48f7 (commit)
      from  ae68cb61741297974f4a76dc7c8fc2ed7a3515c7 (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 6242231510406a9bc0b8cca3a06afab352ff48f7
Author: Thomas Koenig <>
Date:   Sat Apr 30 23:53:49 2022 +0200

    Mention support for IEEE 128-bit long double for Fortran.
            * htdocs/gcc-12/changes.html: Mention support for IEEE
            128-bit long double for Fortran.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 5281c966..c409a17c 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -501,6 +501,15 @@ function Multiply (S1, S2 : Sign) return Sign is
     conforming to the Fortran 2018 standard.  Previous versions
     used <code>OPERATOR</code> which conforms to TS 18508.
+  <li>
+    On POWER systems which support it, the <code>-mabi=ieeelongdouble</code>
+    option now selects the IEEE 128-bit floating point format
+    for <code>REAL(KIND=16)</code>.
+    <code>R16_IBM</code> and <code>R16_IEEE</code> have been added to the
+    <code>-fconvert</code> option, the <code>CONVERT</code> specifyer of
+    the <code>OPEN</code> statement and the <code>GFORTRAN_CONVERT_UNIT</code>
+    environment variable.
+  </li>
 <!-- <h3 id="go">Go</h3> -->


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


                 reply	other threads:[~2022-04-30 21:55 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).