public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <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: Thu, 22 Nov 2012 13:06:00 -0000	[thread overview]
Message-ID: <bug-38785-4-CAaQQMljUi@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 #38 from Jan Hubicka <hubicka at gcc dot gnu.org> 2012-11-22 13:05:38 UTC ---
yet another variant...
void
f (int i, long *a, long *b)
{
  int sum = 0;
  for (; --i >=  0; a++, b++)
    {
  b[i] = 0;
#define PART(I) if (t()) sum+=100+I;
  PART (1);
  PART (2);
  PART (3);
  PART (4);
  PART (5);
  PART (6);
  tt (sum);
    }
}
leads to...
Starting insert iteration 1
Could not find SSA_NAME representative for expression:{plus_expr,sum_8,101}
Created SSA_NAME representative pretmp_98 for expression:{plus_expr,sum_8,101}
Could not find SSA_NAME representative for expression:{plus_expr,pretmp_98,102}
Created SSA_NAME representative pretmp_99 for
expression:{plus_expr,pretmp_98,102}
Could not find SSA_NAME representative for expression:{plus_expr,pretmp_99,103}
Created SSA_NAME representative pretmp_100 for
expression:{plus_expr,pretmp_99,103}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_100,104}
Created SSA_NAME representative pretmp_101 for
expression:{plus_expr,pretmp_100,104}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_101,105}
Created SSA_NAME representative pretmp_102 for
expression:{plus_expr,pretmp_101,105}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_100,105}
Created SSA_NAME representative pretmp_103 for
expression:{plus_expr,pretmp_100,105}
Could not find SSA_NAME representative for expression:{plus_expr,pretmp_99,104}
Created SSA_NAME representative pretmp_104 for
expression:{plus_expr,pretmp_99,104}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_104,105}
Created SSA_NAME representative pretmp_105 for
expression:{plus_expr,pretmp_104,105}
Could not find SSA_NAME representative for expression:{plus_expr,pretmp_99,105}
Created SSA_NAME representative pretmp_106 for
expression:{plus_expr,pretmp_99,105}
Could not find SSA_NAME representative for expression:{plus_expr,pretmp_98,103}
Created SSA_NAME representative pretmp_107 for
expression:{plus_expr,pretmp_98,103}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_107,104}
Created SSA_NAME representative pretmp_108 for
expression:{plus_expr,pretmp_107,104}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_108,105}
Created SSA_NAME representative pretmp_109 for
expression:{plus_expr,pretmp_108,105}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_107,105}
Created SSA_NAME representative pretmp_110 for
expression:{plus_expr,pretmp_107,105}
Could not find SSA_NAME representative for expression:{plus_expr,pretmp_98,104}
Created SSA_NAME representative pretmp_111 for
expression:{plus_expr,pretmp_98,104}
Could not find SSA_NAME representative for
expression:{plus_expr,pretmp_111,105}

that eventually leads to a lot of unused pretmp vars.


  parent reply	other threads:[~2012-11-22 13:06 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
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 [this message]
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-CAaQQMljUi@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).