public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
* gcc-wwwdocs branch master updated. 678d81989495be462debca7c1274e98b231ab6bb
@ 2019-11-27 13:49 markeggleston
  0 siblings, 0 replies; only message in thread
From: markeggleston @ 2019-11-27 13:49 UTC (permalink / raw)
  To: gcc-cvs-wwwdocs

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  678d81989495be462debca7c1274e98b231ab6bb (commit)
      from  d3fe522f132d49424843d7f36f992603131727a3 (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 678d81989495be462debca7c1274e98b231ab6bb
Author: Mark Eggleston <markeggleston@codethink.com>
Date:   Tue Nov 26 10:12:44 2019 +0000

    Update Fortran changes
    
    Legacy extensions: default widths in formats, blank item following last
    comma in formats, automatics in equivalence, dec comparisons.  Character
    type names in error and warning messages.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 52eb303..3a33e20 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -206,6 +206,45 @@ a work-in-progress.</p>
     with <code>-std=legacy</code>.  <code>-Wargument-mismatch</code>
     has been removed.
   </li>
+  <li>
+    Legacy extensions:
+    <ul>
+      <li>
+        For formatted input/output, if the explicit widths after the data-edit
+        descriptors <code>I</code>, <code>F</code> and <code>G</code> have been
+        omitted, default widths are used.
+      <li>
+        A blank format item at the end of a format specification, i.e. nothing
+        following the final comma, is allowed.  Use the option
+        <code>-fdec-blank-format-item</code>, this options is implied with
+        <code>-fdec</code>.
+      </li>
+      <li>
+        The existing support for <code>AUTOMATIC</code> and <code>STATIC</code>
+        attributes has been extended to allow variables with the
+        <code>AUTOMATIC</code> attribute to be used in <code>EQUIVALENCE</code>
+        statements. Use <code>-fdec-static</code>, this option is implied by
+        <code>-fdec</code>.
+      </li>
+      <li>
+        Allow character literals in assignments and <code>DATA</code> statements
+        for numeric (<code>INTEGER</code>, <code>REAL</code>, or
+        <code>COMPLEX</code>) or <code>LOGICAL</code> variables.  Use the option
+        <code>-fdec-char-conversions</code>, this options is implied with
+        <code>-fdec</code>.
+      </li>
+      <li>
+        DEC comparisons, i.e. allow Hollerith constants to be used in comparisons
+        with <code>INTEGER</code>, <code>REAL</code>, <code>COMPLEX</code> and
+        <code>CHARACTER</code> expressions. Use the option <code>-fdec</code>.
+      </li>
+    </ul>
+    <li>
+      Character type names in errors and warnings now include <code>len</code>
+      in addition to <code>kind</code>; <code>*</code> is used for assumed
+      length. The kind is omitted if it is the default kind. Examples:
+      <code>CHARACTER(12)</code>, <code>CHARACTER(6,4)</code>.
+    </li>
 </ul>
 <!-- <h3 id="go">Go</h3> -->
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-10/changes.html |   39 +++++++++++++++++++++++++++++++++++++++
 1 files changed, 39 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-11-27 13:49 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-27 13:49 gcc-wwwdocs branch master updated. 678d81989495be462debca7c1274e98b231ab6bb markeggleston

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).