public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: burnus@gcc.gnu.org
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 7209696136bc42b939efd5daabde1d123e1d5cf9
Date: Thu, 16 Jan 2020 07:48:00 -0000	[thread overview]
Message-ID: <20200116074823.45762.qmail@sourceware.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]

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  7209696136bc42b939efd5daabde1d123e1d5cf9 (commit)
      from  ab05e7b463441cc48c6bc8da4aad45f741188d95 (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 7209696136bc42b939efd5daabde1d123e1d5cf9
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Jan 16 08:46:33 2020 +0100

    PR93253 – Document BOZ changes
    
    2019-01-16  Steven G. Kargl  <kargl@gcc.gnu.org
                Tobias Burnus  <tobias@codesourcery.com>
    
            * htdocs/gcc-10/changes.html (Fortran): Document BOZ changes.

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 5c25195..76a4ed9 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -268,6 +268,16 @@ a work-in-progress.</p>
     has been removed.
   </li>
   <li>
+    The handling of a BOZ literal constant has been reworked to provide
+    better conformance to the Fortran 2008 and 2018 standards.  In these
+    Fortran standards, a BOZ literal constant is a typeless and kindless
+    entity.  As a part of the rework, documented and undocumented
+    extensions to the Fortran standard now emit errors during compilation.
+    Some of these extensions are permitted with the
+    <code>-fallow-invalid-boz</code>, where the error is degraded to a
+    warning and the code is compiled as with older gfortran.
+  <li>
+  <li>
     At any optimization level except<code>-Os</code>, gfortran now
     uses inline packing for arguments instead of calling a library
     routine.  If the source contains a large number of arguments that

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-01-16  7:48 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:
  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=20200116074823.45762.qmail@sourceware.org \
    --to=burnus@gcc.gnu.org \
    --cc=gcc-cvs-wwwdocs@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).