public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. de64311d067a34afbdeda88b957f82b074082506 Date: Fri, 10 Jul 2020 05:50:35 +0000 (GMT) [thread overview] Message-ID: <20200710055035.59DBC3857C7C@sourceware.org> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1583 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 de64311d067a34afbdeda88b957f82b074082506 (commit) from 6e666ed1575fc76cc67c9ba9495e0ee053786ac6 (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 de64311d067a34afbdeda88b957f82b074082506 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Fri Jul 10 07:49:39 2020 +0200 Complete note on -fallow-invalid-boz. diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html index 4e5f6139..2b773f1d 100644 --- a/htdocs/gcc-10/changes.html +++ b/htdocs/gcc-10/changes.html @@ -572,7 +572,7 @@ int get_naïve_pi() { 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 + <code>-fallow-invalid-boz</code> option, which degrades the error to a warning and the code is compiled as with older gfortran. </li> <li> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-07-10 5:50 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=20200710055035.59DBC3857C7C@sourceware.org \ --to=gerald@sourceware.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: linkBe 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).