public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 7.3.0/gentoo/
Date: Sat, 18 Aug 2018 20:00:27 +0000 (UTC)	[thread overview]
Message-ID: <1534622116.add3fe56a47bed5c2330edd600d2c468fec63b2e.slyfox@gentoo> (raw)

commit:     add3fe56a47bed5c2330edd600d2c468fec63b2e
Author:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 18 19:55:16 2018 +0000
Commit:     Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Aug 18 19:55:16 2018 +0000
URL:        https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=add3fe56

7.3.0: fix building against isl-0.20 (PR86724)

Bug: https://bugs.gentoo.org/662500
Bug: https://gcc.gnu.org/PR86724
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>

 7.3.0/gentoo/97_all_isl-include.patch | 35 +++++++++++++++++++++++++++++++++++
 7.3.0/gentoo/README.history           |  2 ++
 2 files changed, 37 insertions(+)

diff --git a/7.3.0/gentoo/97_all_isl-include.patch b/7.3.0/gentoo/97_all_isl-include.patch
new file mode 100644
index 0000000..bb3bcee
--- /dev/null
+++ b/7.3.0/gentoo/97_all_isl-include.patch
@@ -0,0 +1,35 @@
+https://bugs.gentoo.org/662500
+https://gcc.gnu.org/PR86724
+
+From d6470854446446a4e8b3b958a00e5013ed86ae7f Mon Sep 17 00:00:00 2001
+From: rguenth <rguenth@138bc75d-0d04-0410-961f-82ee72b054a4>
+Date: Wed, 1 Aug 2018 07:21:08 +0000
+Subject: [PATCH] 2018-08-01  Richard Biener  <rguenther@suse.de>
+
+	PR bootstrap/86724
+	* graphite.h: Include isl/id.h and isl/space.h to allow build
+	with ISL 0.20.
+
+
+git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@263193 138bc75d-0d04-0410-961f-82ee72b054a4
+---
+ gcc/ChangeLog  | 6 ++++++
+ gcc/graphite.h | 2 ++
+ 2 files changed, 8 insertions(+)
+
+diff --git a/gcc/graphite.h b/gcc/graphite.h
+index 4e0e58c60ab..be0a22b3894 100644
+--- a/gcc/graphite.h
++++ b/gcc/graphite.h
+@@ -37,6 +37,8 @@ along with GCC; see the file COPYING3.  If not see
+ #include <isl/schedule.h>
+ #include <isl/ast_build.h>
+ #include <isl/schedule_node.h>
++#include <isl/id.h>
++#include <isl/space.h>
+ 
+ typedef struct poly_dr *poly_dr_p;
+ 
+-- 
+2.18.0
+

diff --git a/7.3.0/gentoo/README.history b/7.3.0/gentoo/README.history
index 3d29449..6a8069b 100644
--- a/7.3.0/gentoo/README.history
+++ b/7.3.0/gentoo/README.history
@@ -1,3 +1,5 @@
+1.6		18 Aug 2018
+	+ 97_all_isl-include.patch
 1.5		17 Aug 2018
 	+ 94_all_libgo-remove-ustat.h-glibc-2.28.patch
 	+ 95_all_libsanitizer-avoidustat.h-glibc-2.28-part-1.patch


             reply	other threads:[~2018-08-18 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-18 20:00 Sergei Trofimovich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-27  9:32 [gentoo-commits] proj/gcc-patches:master commit in: 7.3.0/gentoo/ Sergei Trofimovich
2018-10-20  9:40 Sergei Trofimovich
2018-10-18 22:13 Sergei Trofimovich
2018-09-30 22:25 Sergei Trofimovich
2018-09-23 20:55 Sergei Trofimovich
2018-08-26 12:16 Sergei Trofimovich
2018-08-16 23:13 Sergei Trofimovich
2018-08-15 21:36 Sergei Trofimovich

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=1534622116.add3fe56a47bed5c2330edd600d2c468fec63b2e.slyfox@gentoo \
    --to=slyfox@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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