public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gcc-help@gcc.gnu.org
Subject: CLooG version for trunk
Date: Fri, 04 Nov 2011 01:56:00 -0000	[thread overview]
Message-ID: <20111103200533.1d208b76@gentoo.org> (raw)

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

Very late in stage 1 of 4.6 development an attempt was made to change the
default version of CLooG needed for graphite support from the cloog-ppl
(0.15) branch to the official CLooG (0.16) releases with the ISL backend.  I
believe it was rejected because of lack of testing - a change like that
should have been made earlier in stage 1 to ensure any regressions were
caught.

Now here we are late in stage 1 of 4.7 development and again I see no changes
made in this area.  Did I miss them or are we going to be stuck with
cloog-ppl for another release cycle?  As ppl continues to develop,
maintaining cloog-ppl gets to be more of a burden, and it appears everyone
involved with graphite in GCC is using the ISL backend.  It's hard enough to
get graphite bugs fixed in the branch they're reported in, so much so that
I've stopped reporting them.  If the development team isn't even using the
same libraries and backends as the users then I don't see how the situation
can improve.


-- 
fonts, gcc-porting,                  it makes no sense how it makes no sense
toolchain, wxwidgets                           but i'll take it free anytime
@ gentoo.org                EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2011-11-04  1:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20111103200533.1d208b76@gentoo.org \
    --to=dirtyepic@gentoo.org \
    --cc=gcc-help@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).