From: Tobias Burnus <burnus@net-b.de>
To: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>,
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: Re: [wwwdocs] gcc-5/changes.html: Graphite - CLooG removal; Fortran - update
Date: Tue, 30 Dec 2014 18:36:00 -0000 [thread overview]
Message-ID: <54A2EC7C.4000304@net-b.de> (raw)
In-Reply-To: <20141112105247.GC27434@physik.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
On 12 November 2014, Tobias Burnus wrote:
> Hi all, hi Gerald, hi Tobias and Roman,
>
> the patch updates gcc-5/changes.html; the Fortran bits are obvious.
I have now also committed a patch for Graphite – slightly modified; the
Fortran patch has been committed before.
Attached is the Graphite part, which I have just committed:
https://gcc.gnu.org/gcc-5/changes.html
Tobias
[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 746 bytes --]
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.54
diff -p -u -r1.54 changes.html
--- changes.html 26 Dec 2014 15:55:05 -0000 1.54
+++ changes.html 30 Dec 2014 18:10:31 -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>The Graphite framework for loop optimizations no longer requires the
+ CLooG library, only ISL version 0.14 (recommended) or 0.12.2. The
+ installation manual contains more information about requirements to
+ build GCC.</li>
</ul>
<h2 id="general">General Optimizer Improvements</h2>
next prev parent reply other threads:[~2014-12-30 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 10:54 Tobias Burnus
2014-12-30 18:36 ` Tobias Burnus [this message]
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=54A2EC7C.4000304@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gareevroman@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeiferdotcom \
--cc=tobias.burnus@physik.fu-berlin.de \
--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).