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 middle-end/33966] Revision 129625 caused 11% slowdown on 200.sixtrack Date: Thu, 01 Nov 2007 11:36:00 -0000 [thread overview] Message-ID: <20071101113606.24296.qmail@sourceware.org> (raw) In-Reply-To: <bug-33966-682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2007-11-01 11:36 ------- Note I didn't experience any sixtrack regression (-O3 and -O3 -funroll-loops -ffast-math) on Opteron. This is very likely a partitioning issue, as the --param max-aliased-vops is different for -O2 vs. -O3 and sixtrack likely "lived on the edge" with the -O2 setting. The patch mainly changed which variables with the same partitioning score are considered for partitioning. So if at all, this is a partitioning/scoring bug. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC|rguenther at suse dot de |rguenth at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33966
next prev parent reply other threads:[~2007-11-01 11:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-01 4:26 [Bug middle-end/33966] New: Revision 129625 caused 1% " hjl at lucon dot org 2007-11-01 10:23 ` [Bug middle-end/33966] Revision 129625 caused 11% " ubizjak at gmail dot com 2007-11-01 11:36 ` rguenth at gcc dot gnu dot org [this message] 2007-11-01 11:40 ` rguenth at gcc dot gnu dot org [not found] <bug-33966-4@http.gcc.gnu.org/bugzilla/> 2012-01-28 3:45 ` pinskia at gcc dot gnu.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=20071101113606.24296.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: linkBe 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).