public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Guenther <richard.guenther@gmail.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-patches@gcc.gnu.org, Sebastian Pop <spop@gcc.gnu.org>
Subject: Re: [vta, graphite, PR41888, PR41886] get graphite to work with VTA
Date: Sun, 08 Nov 2009 10:10:00 -0000	[thread overview]
Message-ID: <84fc9c000911080204o7b89efa9sa59a5c91334fe186@mail.gmail.com> (raw)
In-Reply-To: <or7hu1h1e0.fsf@livre.localdomain>

On Sun, Nov 8, 2009 at 9:22 AM, Alexandre Oliva <aoliva@redhat.com> wrote:
> This patch adds VTA support to the graphite code.
>
> Besides the expected need for skipping or ignoring debug stmts here and
> there, this required debug uses outside rearranged loops to be detected
> and reset if there aren't non-debug uses that would have introduced PHI
> nodes at join points that would enable them to work.
>
> This patch passed bootstrap-compare on x86_64-linux-gnu along with the
> two patches I've just posted, with an additional patch that enabled
> flag_graphite at -O2.  Building libraries mostly worked; the exceptions
> were a couple of libjava object files that took way too long to compile.
> Is this a known issue with graphite, or some interaction with VTA that I
> should look into?
>
> Is this ok to install?

It looks ok to me, but I'd like to have Sebastian ack it as well.

Thanks,
Richard.

  reply	other threads:[~2009-11-08 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-08  8:45 Alexandre Oliva
2009-11-08 10:10 ` Richard Guenther [this message]
2009-11-09  0:27 ` Sebastian Pop
2009-11-16 23:23   ` Alexandre Oliva
2009-11-17 15:32     ` Sebastian Pop
2009-11-17 19:04       ` Alexandre Oliva
2009-11-17 19:22         ` Sebastian Pop
2009-11-18  6:34           ` Alexandre Oliva

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=84fc9c000911080204o7b89efa9sa59a5c91334fe186@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=aoliva@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=spop@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).