public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: Mikael Morin <morin-mikael@orange.fr>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: *ping* [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12
Date: Sat, 30 Apr 2022 23:56:55 +0200	[thread overview]
Message-ID: <c0af93d8-3e39-d9f4-3458-fbb897f1afb5@netcologne.de> (raw)
In-Reply-To: <3f701c0a-d0bd-bafd-f24d-6f727c18c379@orange.fr>

Hi Mikael,

> OK in any case.  Anything is better than nothing.

Here is what I committed, with one final tweak.

Thanks!

Best regards

	Thomas

--- 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>
+  <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>
  </ul>



      reply	other threads:[~2022-04-30 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 16:41 Thomas Koenig
2022-04-29 20:10 ` *ping* " Thomas Koenig
2022-04-30 15:37   ` Mikael Morin
2022-04-30 21:56     ` Thomas Koenig [this message]

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=c0af93d8-3e39-d9f4-3458-fbb897f1afb5@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=morin-mikael@orange.fr \
    /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: 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).