public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44423] [4.5/4.6 Regression] Massive performance regression in SSE code due to SRA
Date: Tue, 08 Jun 2010 14:03:00 -0000 [thread overview]
Message-ID: <20100608140300.18230.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44423-2736@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from rguenth at gcc dot gnu dot org 2010-06-08 14:02 -------
(In reply to comment #5)
> (In reply to comment #2)
> > We have (4.4):
> >
> > <bb 2>:
> > va.f[0] = a->r;
> > va.f[1] = a->g;
> > va.f[2] = a->b;
> > va.f[3] = 0.0;
> > pretmp.40 = va.v;
> > ivtmp.61 = 0;
>
> [...]
>
> Could you please tell me the compiler flag(s) needed to produce this kind of
> information? That seems much more useful for debugging and chasing performance
> bottlenecks than assembler dumps...
-fdump-tree-all will leave you with a hunded dump files, program state
after each individual tree optimization pass. -da will add dumps after
each RTL pass.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44423
next prev parent reply other threads:[~2010-06-08 14:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 10:17 [Bug regression/44423] New: [4.5/4.6] Massive performance regression in SSE code martin at mpa-garching dot mpg dot de
2010-06-05 10:18 ` [Bug regression/44423] " martin at mpa-garching dot mpg dot de
2010-06-05 10:47 ` rguenth at gcc dot gnu dot org
2010-06-05 10:56 ` [Bug tree-optimization/44423] [4.5/4.6 Regression] Massive performance regression in SSE code due to SRA rguenth at gcc dot gnu dot org
2010-06-08 13:16 ` jamborm at gcc dot gnu dot org
2010-06-08 13:54 ` martin at mpa-garching dot mpg dot de
2010-06-08 14:03 ` rguenth at gcc dot gnu dot org [this message]
2010-06-08 14:29 ` jamborm at gcc dot gnu dot org
2010-06-08 14:51 ` rguenth at gcc dot gnu dot org
2010-06-08 15:00 ` jamborm at gcc dot gnu dot org
2010-06-08 15:11 ` rguenth at gcc dot gnu dot org
2010-06-09 9:03 ` jamborm at gcc dot gnu dot org
2010-06-09 9:06 ` jamborm at gcc dot gnu dot org
2010-06-09 11:21 ` jamborm at gcc dot gnu dot org
2010-06-09 12:06 ` martin at mpa-garching dot mpg dot de
2010-06-14 12:40 ` jamborm at gcc dot gnu dot org
2010-06-14 12:46 ` martin at mpa-garching dot mpg dot de
2010-06-14 12:50 ` jamborm at gcc dot gnu dot org
2010-06-15 9:49 ` jamborm at gcc dot gnu dot org
2010-06-15 10:04 ` jamborm 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=20100608140300.18230.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).