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/38785] [4.5/4.6/4.7/4.8 Regression] huge performance regression on EEMBC bitmnp01
Date: Tue, 20 Nov 2012 21:01:00 -0000 [thread overview]
Message-ID: <bug-38785-4-FNXw5Ab4TE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-38785-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38785
--- Comment #34 from Igor Zamyatin <izamyatin at gmail dot com> 2012-11-20 21:00:39 UTC ---
(In reply to comment #32)
> Would be possible to double check if this problem is still fixed after the fix
> to the tree-ssa-pre patch?
Unfortunately the regression happened after the fix...
next prev parent reply other threads:[~2012-11-20 21:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-38785-4@http.gcc.gnu.org/bugzilla/>
2011-06-27 13:41 ` [Bug tree-optimization/38785] [4.3/4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-01-16 13:21 ` [Bug tree-optimization/38785] [4.4/4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-03-13 14:33 ` [Bug tree-optimization/38785] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-04-28 1:59 ` mkuvyrkov at gcc dot gnu.org
2012-04-28 2:13 ` mkuvyrkov at gcc dot gnu.org
2012-05-02 10:41 ` rguenth at gcc dot gnu.org
2012-11-16 17:51 ` hubicka at gcc dot gnu.org
2012-11-16 18:01 ` hubicka at gcc dot gnu.org
2012-11-20 21:01 ` izamyatin at gmail dot com [this message]
2012-11-21 17:57 ` hubicka at gcc dot gnu.org
2012-11-21 18:00 ` amylaar at gcc dot gnu.org
2012-11-22 9:51 ` hubicka at gcc dot gnu.org
2012-11-22 13:06 ` hubicka at gcc dot gnu.org
2013-03-22 14:47 ` [Bug tree-optimization/38785] [4.5/4.6/4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-05-31 10:59 ` [Bug tree-optimization/38785] [4.5/4.7/4.8/4.9 " jakub at gcc dot gnu.org
2013-10-16 9:50 ` jakub at gcc dot gnu.org
2014-05-22 9:07 ` [Bug tree-optimization/38785] [4.5/4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:42 ` [Bug tree-optimization/38785] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-06-23 8:26 ` [Bug tree-optimization/38785] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:09 ` [Bug tree-optimization/38785] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:35 ` jakub at gcc dot gnu.org
2021-05-04 12:32 ` [Bug tree-optimization/38785] [8/9/10/11/12 " rguenth at gcc dot gnu.org
2021-05-14 9:46 ` [Bug tree-optimization/38785] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01 8:04 ` rguenth at gcc dot gnu.org
2022-05-27 9:34 ` [Bug tree-optimization/38785] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:29 ` jakub at gcc dot gnu.org
2023-07-07 10:29 ` [Bug tree-optimization/38785] [11/12/13/14 " rguenth 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-38785-4-FNXw5Ab4TE@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).