public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@net-b.de>
To: gcc-patches <gcc-patches@gcc.gnu.org>,
	gfortran <fortran@gcc.gnu.org>,
	 Gerald Pfeifer <gerald@pfeifer.com>
Subject: [wwwdocs, committed] gcc-5/changes.html: Update Fortran section
Date: Sun, 31 Aug 2014 20:37:00 -0000	[thread overview]
Message-ID: <54038778.7050308@net-b.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 151 bytes --]

Dear all,

I have committed the attached patch. Comment and suggestions are welcome!

See also: https://gcc.gnu.org/gcc-5/changes.html#fortran

Tobias

[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 2364 bytes --]

Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.7
diff -u -p -r1.7 changes.html
--- changes.html	26 Aug 2014 17:18:40 -0000	1.7
+++ changes.html	31 Aug 2014 20:34:49 -0000
@@ -91,6 +91,18 @@
 
 <h3 id="fortran">Fortran</h3>
   <ul>
+    <li>Incomplete support for colorizing diagnostics emitted by gfortran has
+      been added. The <code><a
+      href="https://gcc.gnu.org/onlinedocs/gcc/Language-Independent-Options.html#index-fdiagnostics-color-256"
+      >-fdiagnostics-color=</a>auto</code> will enable it when outputting to
+      terminals, <code>-fdiagnostics-color=always</code> unconditionally. The
+      <code>GCC_COLORS</code> environment variable can be used to customize the
+      colors or disable coloring. If <code>GCC_COLORS</code> variable is present
+      in the environment, the default is <code>-fdiagnostics-color=auto</code>,
+      otherwise <code>-fdiagnostics-color=never</code>.</li>
+    <li>The <code>-Wuse-without-only</code> option has been added to warn when a
+      <code>USE</code> statement has no <code>ONLY</code> qualifier and, thus,
+      implicitly imports all public entities of the used module.</li>
     <li><a href="https://gcc.gnu.org/wiki/Fortran2003Status">Fortran 2003</a>:
     <ul>
       <li>The intrinsic IEEE modules (<code>IEEE_FEATURES</code>,
@@ -99,11 +111,14 @@
     </ul></li>
     <li><a href="https://gcc.gnu.org/wiki/Fortran2008Status">Fortran 2008</a>:
     <ul>
-      <li>Coarrays: Full experimental support of Fortran 2008's coarrays with
+      <li><a href="https://gcc.gnu.org/wiki/Coarray">Coarrays</a>: Full
+	experimental support of Fortran 2008's coarrays with
 	<code>-fcoarray=lib</code> except for locking and allocatable/pointer
-	components of derived-type coarrays. Note that GCC currently only ships
-	with a library which only supports a single image
-	(<code>libcaf_single</code>).</li>
+	components of derived-type coarrays.  GCC currently only ships with a
+	single-image library (<code>libcaf_single</code>), but
+	mult-image support based on MPI and GASNet is provided by the libraries
+	of the <a href="http://www.opencoarrays.org/">OpenCoarrays project</a>. 
+	</li>
     </ul></li>
     <li>TS18508 Additional Parallel Features in Fortran:
     <ul>

             reply	other threads:[~2014-08-31 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31 20:37 Tobias Burnus [this message]
2015-05-01 22:44 ` Gerald Pfeifer
2015-05-03 11:29   ` Tobias Burnus

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=54038778.7050308@net-b.de \
    --to=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    /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).