public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jack Howarth <howarth@bromo.med.uc.edu>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: more graphite merges before gcc 4.5 branch?
Date: Fri, 13 Nov 2009 15:11:00 -0000	[thread overview]
Message-ID: <20091113151059.GB18978@bromo.med.uc.edu> (raw)
In-Reply-To: <303e1d290911121023m5a82eb9sfd3d8236c8e4cb27@mail.gmail.com>

On Thu, Nov 12, 2009 at 01:23:30PM -0500, David Edelsohn wrote:
> 
> 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

David,
    Thanks for the information. Since FSF gcc on darwin is unlikely
to gain LTO any time soon (unless it comes in the form of DragonEgg
http://dragonegg.llvm.org/), I was hoping that we might realize
some performnce improvements via graphite (or at least see that
the none of the Polyhedron 2005 benchmarks degrade under its
optimizations) in gcc 4.5.
          Jack

      reply	other threads:[~2009-11-13 15:11 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
2009-11-13 15:11   ` Jack Howarth [this message]

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=20091113151059.GB18978@bromo.med.uc.edu \
    --to=howarth@bromo.med.uc.edu \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@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).