public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Sebastian Pop" <sebpop@gmail.com>
To: gcc-bugzilla@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug middle-end/38846] New: [Graphite] 70% slower using -floop* than without graphite (gas_dyn of Polyhedron)
Date: Wed, 14 Jan 2009 18:42:00 -0000	[thread overview]
Message-ID: <cb9d34b20901141041s5141c250ja859c0a4e7e37468@mail.gmail.com> (raw)
In-Reply-To: <bug-38846-13404@http.gcc.gnu.org/bugzilla/>

Hi,

Thanks for this report.  Please also test with the code of graphite
branch that contains a
patch that schedules several scalar optimizations that can improve the
quality of the code generated.

Thanks,
Sebastian Pop
--
AMD - GNU Tools


  reply	other threads:[~2009-01-14 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 18:26 burnus at gcc dot gnu dot org
2009-01-14 18:42 ` Sebastian Pop [this message]
2009-01-14 18:42 ` [Bug middle-end/38846] " sebpop at gmail dot com
2009-01-14 18:45 ` burnus at gcc dot gnu dot org
2009-01-14 21:16 ` burnus at gcc dot gnu dot org
2009-01-17 18:12 ` dominiq at lps dot ens dot fr
2009-04-24 21:38 ` burnus at gcc dot gnu dot org
2010-02-23 15:29 ` [Bug middle-end/38846] [Graphite] 35% " burnus at gcc dot gnu dot org

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=cb9d34b20901141041s5141c250ja859c0a4e7e37468@mail.gmail.com \
    --to=sebpop@gmail.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).