public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/55623] [ARM] GCC should not prefer long dependency chains, they inhibit performance on superscalar processors
Date: Tue, 11 Dec 2012 16:33:00 -0000 [thread overview]
Message-ID: <bug-55623-4-FJJYWVutw4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55623-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55623
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramana at gcc dot gnu.org
--- Comment #9 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> 2012-12-11 16:33:25 UTC ---
(In reply to comment #8)
> You can also adjust --param tree-reassoc-width or have the target implement
> the sched.reassociation_width target hook (for the default).
I did try it on an A9 when the hook came out and it made bugger all difference
to the benchmarks I cared about on a range of values.
It's possible this might help on some of the newer cores.
ramana
prev parent reply other threads:[~2012-12-11 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 10:00 [Bug tree-optimization/55623] New: " siarhei.siamashka at gmail dot com
2012-12-09 10:01 ` [Bug tree-optimization/55623] " siarhei.siamashka at gmail dot com
2012-12-09 10:48 ` [Bug middle-end/55623] " pinskia at gcc dot gnu.org
2012-12-09 11:19 ` siarhei.siamashka at gmail dot com
2012-12-09 11:22 ` siarhei.siamashka at gmail dot com
2012-12-09 11:36 ` steven at gcc dot gnu.org
2012-12-09 12:13 ` steven at gcc dot gnu.org
2012-12-09 12:15 ` steven at gcc dot gnu.org
2012-12-10 9:47 ` rguenth at gcc dot gnu.org
2012-12-11 16:33 ` ramana at gcc dot gnu.org [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=bug-55623-4-FJJYWVutw4@http.gcc.gnu.org/bugzilla/ \
--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).