From: David Edelsohn <dje.gcc@gmail.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: more graphite merges before gcc 4.5 branch?
Date: Thu, 12 Nov 2009 18:23:00 -0000 [thread overview]
Message-ID: <303e1d290911121023m5a82eb9sfd3d8236c8e4cb27@mail.gmail.com> (raw)
In-Reply-To: <20091112170336.GA7516@bromo.med.uc.edu>
On Thu, Nov 12, 2009 at 12:03 PM, Jack Howarth <howarth@bromo.med.uc.edu> wrote:
> Are there any plans for further merges out of the
> graphite branch before gcc 4.5 is branched? I was
> under the impression that the graphite developers
> originally intended to keep trunk more closely
> synchronized with the graphite branch during the
> gcc 4.5 release cycle and this doesn't seem to have
> happened. It would be a shame to see graphite's
> performance be suboptimal for another release cycle.
Yes, more Graphite merges are planned. The VTA merge broke Graphite
and we are waiting for Alexandre's recent VTA fixes for Graphite to be
updated based on the initial feedback from Sebastian and merged into
the trunk. Then the patches from Graphite can be merged.
Please keep in mind that Graphite is experimental and not a panacea.
If you and your colleagues want Graphite to be able to apply more
high-level loop transformations and want it to be more effective with
better tuning, please help implement the optimizations.
Thanks, David
next prev parent reply other threads:[~2009-11-12 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 17:03 Jack Howarth
2009-11-12 18:23 ` David Edelsohn [this message]
2009-11-13 15:11 ` Jack Howarth
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=303e1d290911121023m5a82eb9sfd3d8236c8e4cb27@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=howarth@bromo.med.uc.edu \
/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).