From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Mike Stump <mikestump@comcast.net>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] [graphite] document that isl-0.16 is supported
Date: Wed, 03 Feb 2016 06:37:00 -0000 [thread overview]
Message-ID: <56B1A040.3060502@embedded-brains.de> (raw)
In-Reply-To: <56B19E52.2030304@embedded-brains.de>
On 03/02/16 07:29, Sebastian Huber wrote:
>
>
> On 02/02/16 19:00, Mike Stump wrote:
>> On Feb 2, 2016, at 2:23 AM, Sebastian
>> Huber<sebastian.huber@embedded-brains.de> wrote:
>>> >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?
>> The latest release, or the one on your system. This is so basic that
>> we expect you to already know this.
>>
>>> >Are the versions in the contrib/download_prerequisites script the
>>> recommended ones?
>> Yes, they are.
>
> If it is so basic to choose the latest release or the one on the
> system, then why uses the contrib/download_prerequisites ancient
> versions, e.g. the six year old GMP 4.3.2?
>
There is exactly one version of GMP, MPC and MPFR available via:
ftp://gcc.gnu.org/pub/gcc/infrastructure/
This doesn't suggest to me that I should use the latest release.
--
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-03 6:37 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
2016-02-02 18:00 ` Mike Stump
2016-02-03 6:29 ` Sebastian Huber
2016-02-03 6:37 ` Sebastian Huber [this message]
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=56B1A040.3060502@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).