public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Thomas Koenig <tkoenig@netcologne.de>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran, doc] Mention new CONVERT options for POWER
Date: Thu, 28 Apr 2022 09:20:14 +0200	[thread overview]
Message-ID: <CAFiYyc1CrF4dx95jQ+N+S+CQ6g9c+=TkDK6Zv29qjsubiZPCiA@mail.gmail.com> (raw)
In-Reply-To: <c5d8b93f-c039-e4cb-7ea6-cdb4e2502f42@netcologne.de>

On Wed, Apr 27, 2022 at 10:34 PM Thomas Koenig via Fortran
<fortran@gcc.gnu.org> wrote:
>
> Hi,
>
> as we say in German "Nicht documentiert ist nicht gemacht", if
> it is not documented, it wasn't done.
>
> So I thought it would be time to document the changes to the various
> ways of specifying CONVERT before gcc12 went out of the door, so
> here is a patch for that.
>
> If that goes in, I will also write up something for gcc-12/changes.html.
>
> OK for trunk?  Suggestions for improvements?

OK for trunk.

Richard.

> Best regards
>
>         Thomas
>
> Document changes to CONVERT for -mabi-ieeelongdouble for POWER
>
> gcc/fortran/ChangeLog:
>
>         * gfortran.texi: Mention r16_ieee and r16_ibm.
>         * invoke.texi: Likewise.

  reply	other threads:[~2022-04-28  7:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27 20:34 Thomas Koenig
2022-04-28  7:20 ` Richard Biener [this message]
2022-04-28 17:17 ` Bernhard Reutner-Fischer
2022-04-29 18:03   ` Thomas Koenig
2022-04-29 23:26     ` Bernhard Reutner-Fischer
2022-05-02  6:32       ` Richard Biener

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='CAFiYyc1CrF4dx95jQ+N+S+CQ6g9c+=TkDK6Zv29qjsubiZPCiA@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tkoenig@netcologne.de \
    /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).