public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
* [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12
@ 2022-04-28 16:41 Thomas Koenig
  2022-04-29 20:10 ` *ping* " Thomas Koenig
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Koenig @ 2022-04-28 16:41 UTC (permalink / raw)
  To: fortran, gcc-patches

[-- Attachment #1: Type: text/plain, Size: 299 bytes --]

Hi,

the attached patch documents the support for IEEE long double for
Fortran.  OK?  Suggestions for better wording?

Best regards

	Thomas


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.

[-- Attachment #2: p-changes.diff --]
[-- Type: text/x-patch, Size: 816 bytes --]

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index e9f132c0..083d713e 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -497,6 +497,14 @@ 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, <code>-mabi=ieeelongdouble</code>
+    now uses IEEE 128-bit 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>
 
 <!-- <h3 id="go">Go</h3> -->

^ permalink raw reply	[flat|nested] 4+ messages in thread

* *ping* [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12
  2022-04-28 16:41 [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12 Thomas Koenig
@ 2022-04-29 20:10 ` Thomas Koenig
  2022-04-30 15:37   ` Mikael Morin
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Koenig @ 2022-04-29 20:10 UTC (permalink / raw)
  To: fortran, gcc-patches


> the attached patch documents the support for IEEE long double for
> Fortran.  OK?  Suggestions for better wording?

I'd like to get this in before the gcc12 release.  It would also
qualify as obviously correct, I think :-) so I'll commit this
on Sunday unless there are any objections.

Patch at

https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593780.html

Best regards

	Thomas

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: *ping* [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12
  2022-04-29 20:10 ` *ping* " Thomas Koenig
@ 2022-04-30 15:37   ` Mikael Morin
  2022-04-30 21:56     ` Thomas Koenig
  0 siblings, 1 reply; 4+ messages in thread
From: Mikael Morin @ 2022-04-30 15:37 UTC (permalink / raw)
  To: Thomas Koenig, fortran, gcc-patches

Le 29/04/2022 à 22:10, Thomas Koenig via Fortran a écrit :
> 
>> the attached patch documents the support for IEEE long double for
>> Fortran.  OK?  Suggestions for better wording?
> 
> I'd like to get this in before the gcc12 release.  It would also
> qualify as obviously correct, I think :-) so I'll commit this
> on Sunday unless there are any objections.
> 
May I suggest to rewrite the first sentence as:
   On POWER systems which support it, the
   <code>-mabi=ieeelongdouble</code> option is now available to use the
   IEEE 128-bit floating point format for <code>REAL(KIND=16)</code>
   types.

OK in any case.  Anything is better than nothing.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: *ping* [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12
  2022-04-30 15:37   ` Mikael Morin
@ 2022-04-30 21:56     ` Thomas Koenig
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Koenig @ 2022-04-30 21:56 UTC (permalink / raw)
  To: Mikael Morin, fortran, gcc-patches

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>



^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-04-30 21:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-28 16:41 [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12 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 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).