public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gcc: fix building w/isl-0.15
Date: Wed, 22 Jul 2015 00:40:00 -0000	[thread overview]
Message-ID: <20150722000224.GI12267@vapier> (raw)
In-Reply-To: <55AE908A.1020603@redhat.com>

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

On 21 Jul 2015 12:33, Jeff Law wrote:
> On 07/14/2015 08:45 AM, Mike Frysinger wrote:
> > ---
> >   gcc/config.in               |  6 ++++++
> >   gcc/configure               | 31 +++++++++++++++++++++++++++++++
> >   gcc/configure.ac            | 14 ++++++++++++++
> >   gcc/graphite-dependences.c  | 14 +++++++-------
> >   gcc/graphite-optimize-isl.c |  8 ++++++--
> >   gcc/graphite-poly.h         |  5 +++++
> >   6 files changed, 69 insertions(+), 9 deletions(-)
>
> Thanks.  I needed Bernhard's follow-up to get a successful build with 
> isl-0.15 installed.
> 
> For testing I verified there were no regressions using bootstrapped 
> compilers built with isl-0.13 vs isl-0.15.  I also verified that GCC 
> would bootstrap with the patch installed, but no ISL installed.

thanks for the extensive testing :).  i largely only validated gcc-5.2 with
with 0.13 and 0.15 and even then was smoke tests (rebuilding itself and other
packages).
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-07-22  0:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 14:45 Mike Frysinger
2015-07-17 11:36 ` [PATCH] gcc/: Fix building with isl-0.15.0; includes Bernhard Reutner-Fischer
2015-07-21 18:42 ` [PATCH] gcc: fix building w/isl-0.15 Jeff Law
2015-07-21 21:11   ` Sebastian Pop
2015-07-21 21:45     ` Mike Stump
2015-07-23 18:11     ` Jeff Law
2015-07-24 22:08       ` Sebastian Pop
2015-07-24 22:42         ` Jeff Law
2015-07-22  0:40   ` Mike Frysinger [this message]
2015-07-19 21:28 james harvey

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=20150722000224.GI12267@vapier \
    --to=vapier@gentoo.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.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).