public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/42216] [4.5 Regression] 464.h264ref peak regressed 20% Date: Mon, 30 Nov 2009 10:54:00 -0000 [thread overview] Message-ID: <20091130105404.19921.qmail@sourceware.org> (raw) In-Reply-To: <bug-42216-10053@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from hjl dot tools at gmail dot com 2009-11-30 10:54 ------- This may be related to revision 154688, which has caused PR 42202. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42216
next prev parent reply other threads:[~2009-11-30 10:54 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-11-29 13:39 [Bug tree-optimization/42216] New: [4.5 Regression] 464.h265ref " rguenth at gcc dot gnu dot org 2009-11-29 13:39 ` [Bug tree-optimization/42216] " rguenth at gcc dot gnu dot org 2009-11-29 17:58 ` rth at gcc dot gnu dot org 2009-11-30 9:58 ` [Bug tree-optimization/42216] [4.5 Regression] 464.h264ref " rguenther at suse dot de 2009-11-30 10:54 ` hjl dot tools at gmail dot com [this message] 2009-12-01 9:58 ` [Bug tree-optimization/42216] [4.5 Regression] rev 15458[78] regress 464.h264ref peak 20% rguenth at gcc dot gnu dot org 2009-12-01 15:27 ` bernds_cb1 at t-online dot de 2009-12-01 15:36 ` rguenther at suse dot de 2009-12-01 16:46 ` [Bug tree-optimization/42216] [4.5 Regression] rev 154688 " rguenth at gcc dot gnu dot org 2009-12-01 17:03 ` rguenth at gcc dot gnu dot org 2009-12-01 17:26 ` bernds_cb1 at t-online dot de 2009-12-01 17:27 ` bernds_cb1 at t-online dot de 2009-12-02 12:15 ` [Bug rtl-optimization/42216] [4.5 Regression] changes in scheduling regress 464.h264ref 20% rguenth at gcc dot gnu dot org 2009-12-02 13:16 ` rguenth at gcc dot gnu dot org 2009-12-02 13:17 ` rguenth at gcc dot gnu dot org 2009-12-02 16:28 ` bernds_cb1 at t-online dot de 2009-12-02 16:29 ` bernds_cb1 at t-online dot de 2009-12-02 16:57 ` rguenth at gcc dot gnu dot org 2009-12-02 17:06 ` bernds_cb1 at t-online dot de 2009-12-02 17:07 ` rguenther at suse dot de 2009-12-04 14:26 ` bernds_cb1 at t-online dot de 2009-12-04 14:35 ` rguenther at suse dot de 2009-12-10 18:03 ` bernds at gcc dot gnu dot org 2009-12-11 21:39 ` rguenth at gcc dot gnu dot org 2010-03-08 11:48 ` rguenth at gcc dot gnu dot org 2010-03-08 23:04 ` bernds_cb1 at t-online dot de 2010-03-09 8:35 ` dominiq at lps dot ens dot fr 2010-03-09 10:31 ` rguenther at suse dot de 2010-03-14 9:34 ` dominiq at lps dot ens dot fr 2010-03-17 9:26 ` bernds at gcc dot gnu dot org 2010-03-18 17:59 ` rguenth 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=20091130105404.19921.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).