public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/31396] Inline code performance much worse than out-of-line
Date: Sat, 12 Jan 2008 19:14:00 -0000	[thread overview]
Message-ID: <20080112190036.889.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31396-14334@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from hubicka at gcc dot gnu dot org  2008-01-12 19:00 -------
Created an attachment (id=14930)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14930&action=view)
tentative fix

I am testing the attached patch.  It is obvious that we should use profile
here.  The PR is most likely regression to 2.95 that used to multiply n_refs by
3 inside loops.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31396


  parent reply	other threads:[~2008-01-12 19:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 22:15 [Bug c/31396] New: " jamagallon at ono dot com
2007-03-29 22:17 ` [Bug c/31396] " jamagallon at ono dot com
2007-03-29 22:18 ` jamagallon at ono dot com
2007-03-29 22:23 ` jamagallon at ono dot com
2007-03-29 22:47 ` [Bug middle-end/31396] " jamagallon at ono dot com
2007-04-03  4:49 ` [Bug rtl-optimization/31396] " pinskia at gcc dot gnu dot org
2007-04-03  5:03 ` pinskia at gcc dot gnu dot org
2007-04-04  7:05 ` ubizjak at gmail dot com
2007-04-04  8:21 ` ubizjak at gmail dot com
2008-01-12 19:14 ` hubicka at gcc dot gnu dot org [this message]
2008-01-16 17:20 ` hubicka at gcc dot gnu dot org
2008-01-16 17:26 ` hubicka at gcc dot gnu dot org
2008-01-18  8:59 ` ubizjak at gmail dot com

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=20080112190036.889.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: 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).