public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "izamyatin at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/52272] [4.7/4.8 regression] Performance regresswion of 410.bwaves on x86. Date: Thu, 29 Mar 2012 11:26:00 -0000 [thread overview] Message-ID: <bug-52272-4-XF0wUUiWyo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52272-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52272 --- Comment #10 from Igor Zamyatin <izamyatin at gmail dot com> 2012-03-29 11:04:27 UTC --- Is it possible to look at the regressed test-case and gcc dumps with -fdump-tree-ivopts-details option w/o that change? Thanks in advance
next prev parent reply other threads:[~2012-03-29 11:05 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-16 8:17 [Bug regression/52272] New: [4.7 " vbyakovl23 at gmail dot com 2012-02-16 8:19 ` [Bug regression/52272] " vbyakovl23 at gmail dot com 2012-02-16 8:26 ` vbyakovl23 at gmail dot com 2012-02-16 10:45 ` [Bug tree-optimization/52272] " rguenth at gcc dot gnu.org 2012-02-16 12:52 ` rguenth at gcc dot gnu.org 2012-02-16 13:10 ` rguenth at gcc dot gnu.org 2012-02-16 14:45 ` vbyakovl23 at gmail dot com 2012-02-20 12:30 ` rguenth at gcc dot gnu.org 2012-02-20 13:06 ` [Bug tree-optimization/52272] [4.7/4.8 " jakub at gcc dot gnu.org 2012-03-26 11:17 ` izamyatin at gmail dot com 2012-03-27 23:45 ` meissner at gcc dot gnu.org 2012-03-29 11:26 ` izamyatin at gmail dot com [this message] 2012-04-19 13:21 ` izamyatin at gmail dot com 2012-04-20 23:18 ` meissner at gcc dot gnu.org 2012-04-20 23:18 ` meissner at gcc dot gnu.org 2012-04-20 23:20 ` meissner at gcc dot gnu.org 2012-04-20 23:21 ` meissner at gcc dot gnu.org 2012-04-20 23:25 ` meissner at gcc dot gnu.org 2012-12-06 16:23 ` [Bug tree-optimization/52272] [4.7/4.8 regression] Performance regression " rguenth at gcc dot gnu.org 2013-02-09 19:15 ` aldyh at gcc dot gnu.org 2013-03-22 14:45 ` [Bug tree-optimization/52272] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2013-05-31 10:59 ` jakub at gcc dot gnu.org 2013-10-16 9:51 ` jakub at gcc dot gnu.org 2013-12-17 8:29 ` amker.cheng at gmail dot com 2014-05-22 9:05 ` [Bug tree-optimization/52272] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:33 ` [Bug tree-optimization/52272] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-06-23 8:26 ` [Bug tree-optimization/52272] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:01 ` [Bug tree-optimization/52272] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:31 ` jakub at gcc dot gnu.org 2015-08-28 9:27 ` amker 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=bug-52272-4-XF0wUUiWyo@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: 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).