public inbox for
help / color / mirror / Atom feed
From: Sandra Loosemore <>
Subject: gcc-wwwdocs branch master updated. f5971f451ae8834e928738bbfe465670aa481cea
Date: Thu, 21 Oct 2021 16:04:51 +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  f5971f451ae8834e928738bbfe465670aa481cea (commit)
      from  b0b0e2c4449d802154ab90bf1d691548c60cc208 (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 f5971f451ae8834e928738bbfe465670aa481cea
Author: Sandra Loosemore <>
Date:   Thu Oct 21 09:00:16 2021 -0700

    GCC 12: Add release note for Fortran TS29113 improvements.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 5be15700..5974b9ba 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -147,7 +147,17 @@ a work-in-progress.</p>
 <!-- <h3 id="d">D</h3> -->
-<!-- <h3 id="fortran">Fortran</h3> -->
+<h3 id="fortran">Fortran</h3>
+  <li>WG5/N1942, "TS 29113 Further Interoperability of Fortran with C",
+    is now fully supported.  In addition to implementing previously
+    missing functionality, such as support for character arguments of
+    length greater than one in functions marked <code>bind(c)</code>
+    and gaps in the handling for assumed-rank arrays, numerous other bugs
+    have been fixed, and an extensive set of new conformance test cases
+    has been added.
+  </li>
 <!-- <h3 id="go">Go</h3> -->


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


                 reply	other threads:[~2021-10-21 16:04 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).