public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: Requesting ISL update
Date: Tue, 15 Sep 2015 17:09:00 -0000	[thread overview]
Message-ID: <CAOC2fq8H6ndEzeQmiCKrH6qa6fbGJUHcxVzy2dGLEmHxhYU0zw@mail.gmail.com> (raw)
In-Reply-To: <55F7ED02.4080008@gmail.com>

On Tue, Sep 15, 2015 at 3:03 AM, JonY wrote:
>
> Hi Achim,
>
> Can you please update ISL for newer versions of GCC?
> http://isl.gforge.inria.fr/ says 0.15 is the latest.
>

PMFJI,

I was setting up a cross compiler this past Sunday under Cygwin, using
GCC 5.1.0. I followed the "BYOI" (Bring your own Infrastructure) path
and ISL 0.15 was my first choice (being the latest), but did not work.
ISL 0.12.2 did work. ISL 15 passes the initial "compatible version of
ISL" check that the GCC configure script does, but the granite code
within GCC doesn't actually compile properly. When I recompiled
without the --with-isl setting in configure, no ISL library was found,
according to the "compatible version of ISL" message again, and the
compiler was a success anyway. I built an OS with it, threw it away
and started over using ISL 0.12.2. Everything worked, and the
resulting OS build (Embedded Xinu for RPi) ran properly.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2015-09-15 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 10:04 JonY
2015-09-15 17:09 ` Michael Enright [this message]
2015-09-15 22:53   ` JonY
2015-09-19  6:35     ` Achim Gratz
2015-09-20 13:17     ` Achim Gratz
2015-09-20 13:46       ` JonY
2015-09-21  9:54       ` Jon TURNEY
2015-09-21 16:28         ` Achim Gratz

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=CAOC2fq8H6ndEzeQmiCKrH6qa6fbGJUHcxVzy2dGLEmHxhYU0zw@mail.gmail.com \
    --to=mike@kmcardiff.com \
    --cc=cygwin@cygwin.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).