public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
To: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Cc: Gerald Pfeifer <gerald@pfeiferdotcom>,
	Tobias Grosser <tobias@grosser.es>,
	Roman Gareev <gareevroman@gmail.com>
Subject: [wwwdocs] gcc-5/changes.html: Graphite - CLooG removal; Fortran - update
Date: Wed, 12 Nov 2014 10:54:00 -0000	[thread overview]
Message-ID: <20141112105247.GC27434@physik.fu-berlin.de> (raw)

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

Hi all, hi Gerald, hi Tobias and Roman,

the patch updates gcc-5/changes.html; the Fortran bits are obvious.

For CLooG:
* That CLooG is no longer needed is the main reason for writing this
  Caveat item.

* Regarding ISL 0.12.2: The recommended version already changed
  2014-02-13 and thus for 4.9 (cf. PR59878); gcc-4.8/changes.html
  had 0.11.1 - and gcc-4.9/changes.html doesn't mention ISL or CLooG.
  I don't know whether the GCC 5 change of using ISL directly instead
  of CLooG with ISL backend causes an explicit requirement of ISL 0.12.2,
  but not using 0.11.x is definitely a good idea.

* It is planned to additionally support ISL 0.14.0 (which fixes
  PR62289) - but which is API incompatile to ISL 0.12.2. Whence that
  patch is in, one has to re-write this item.

OK? Comments? Suggestions?

* * *

BTW: There is currently no version check in configure for ISL, maybe one
should add one for include/isl/stdint.h, which defines:
#define _GENERATED_STDINT_H "isl 0.12.2"
For the in-tree build, one could check isl/GIT_HEAD_ID or
isl/configure{,.ac}.

Tobias

[-- Attachment #2: gcc5.diff --]
[-- Type: text/x-diff, Size: 1989 bytes --]

Index: htdocs/gcc-5/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.20
diff -p -u -r1.20 changes.html
--- htdocs/gcc-5/changes.html	27 Oct 2014 18:05:26 -0000	1.20
+++ htdocs/gcc-5/changes.html	12 Nov 2014 09:17:54 -0000
@@ -16,6 +16,10 @@
   <ul>
     <li>The default mode for C is now <code>-std=gnu11</code> instead of
         <code>-std=gnu89</code>.</li>
+    <li>To enable the Graphite framework for loop optimizations, you now need
+        ISL version 0.12.2; the CLooG library is no longer required.  The
+        installation manual contains more information about requirements to
+        build GCC.</li>
   </ul>
 
 <h2 id="general">General Optimizer Improvements</h2>
@@ -201,18 +205,23 @@
 	<code>-fcoarray=lib</code> except for locking and allocatable/pointer
 	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
+	multi-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>
       <li>Support for the collective intrinsic subroutines <code>CO_MAX</code>,
-	<code>CO_MIN</code> and <code>CO_SUM</code> has been added,
-	including <code>-fcoarray=lib</code> support.</li>
+	<code>CO_MIN</code>, <code>CO_SUM</code>, <code>CO_BROADCAST</code> and
+	<code>CO_REDUCE</code>has been added, including
+	<code>-fcoarray=lib</code> support.</li>
       <li>Support for the new atomic intrinsics has been added, including
 	<code>-fcoarray=lib</code> support.</li>
     </ul></li>
+    <li>Fortran 2015:
+    <ul>
+      <li>Support for <code>IMPLICIT NONE (external, type)</code>.</li>
+    </ul></li>
   </ul>
 
 <!-- h3 id="go">Go</h3 -->

             reply	other threads:[~2014-11-12 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 10:54 Tobias Burnus [this message]
2014-12-30 18:36 ` Tobias Burnus
2015-04-09 23:31 ` Gerald Pfeifer

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=20141112105247.GC27434@physik.fu-berlin.de \
    --to=tobias.burnus@physik.fu-berlin.de \
    --cc=fortran@gcc.gnu.org \
    --cc=gareevroman@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeiferdotcom \
    --cc=tobias@grosser.es \
    /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).