public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: *ping* [patch, wwwdocs] Mention POWER IEEE128 changes for gcc 12
Date: Fri, 29 Apr 2022 22:10:52 +0200	[thread overview]
Message-ID: <340d0801-3266-f384-c267-63683c7d60b0@netcologne.de> (raw)
In-Reply-To: <9c3e420f-afcf-f2ff-8ea7-35da6f7d7675@netcologne.de>


> 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

  reply	other threads:[~2022-04-29 20:10 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 ` Thomas Koenig [this message]
2022-04-30 15:37   ` *ping* " Mikael Morin
2022-04-30 21:56     ` Thomas Koenig

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=340d0801-3266-f384-c267-63683c7d60b0@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    /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).