From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] [graphite] document that isl-0.16 is supported
Date: Tue, 02 Feb 2016 10:23:00 -0000 [thread overview]
Message-ID: <56B08385.3090304@embedded-brains.de> (raw)
In-Reply-To: <AD206AD9-8245-4AE5-9440-CF4928875C0A@comcast.net>
On 01/02/16 19:27, Mike Stump wrote:
> On Jan 29, 2016, at 8:10 AM, Sebastian Pop<s.pop@samsung.com> wrote:
>> >diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
>> >index 062f42c..3df7974 100644
>> >--- a/gcc/doc/install.texi
>> >+++ b/gcc/doc/install.texi
>> >@@ -383,7 +383,7 @@ installed but it is not in your default library search path, the
>> >@option{--with-mpc} configure option should be used. See also
>> >@option{--with-mpc-lib} and @option{--with-mpc-include}.
>> >
>> >-@item isl Library version 0.15 or 0.14.
>> >+@item isl Library version 0.16, 0.15, or 0.14.
> So, they should commit to compatibility with apis vended, and if they do, I think we should say 0.14 or later. This doesn’t mean that we won’t need fixes from time to time or that they will always do this, but generally that is true. If we (they) deviate from this,_then_ we document the exceptions. If release after release goes out, with all newer versions not working, then the list of known good versions is best; but, I’d say that something is terribly broken if we had to do that.
It would be good to have a recommended version as well (similar for
cloog, gmp, mpc and mpfr). If you present me three versions which one
should I choose as a naive user? Are the versions in the
contrib/download_prerequisites script the recommended ones?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
next prev parent reply other threads:[~2016-02-02 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 16:08 Sebastian Pop
2016-02-01 18:30 ` Mike Stump
2016-02-02 10:23 ` Sebastian Huber [this message]
2016-02-02 18:00 ` Mike Stump
2016-02-03 6:29 ` Sebastian Huber
2016-02-03 6:37 ` Sebastian Huber
2016-02-03 19:04 ` Mike Stump
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=56B08385.3090304@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).