public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vbyakovl23 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52241] New: Performance degradation of 447.dealII on corei7 at spec2006_base32.
Date: Tue, 14 Feb 2012 08:10:00 -0000	[thread overview]
Message-ID: <bug-52241-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52241
           Summary: Performance degradation of 447.dealII on corei7 at
                    spec2006_base32.
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: vbyakovl23@gmail.com


Guilty commit

c1e8b3edf7b5038f070c7a9732e58d066081a636 is the first bad commit
commit c1e8b3edf7b5038f070c7a9732e58d066081a636
Author: bkoz <bkoz@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Mon Jan 23 23:12:01 2012 +0000

caused performance degradation of 447.dealII benchspec 2006.It was happened
because there are no inlining a library routine '_Rb_tree_node_base' from
libstdc++-v3/src/tree.cc

const _Rb_tree_node_base*  _Rb_tree_increment(const _Rb_tree_node_base* __x)
throw ()
{    
  return Rb_tree_increment(const_cast&lt;_Rb_tree_node_base*&gt;(_x));
}

I found out that the degradation is caused by absence of -fPIC flag in
compilation command line. If I add the flag to command line the inlining is
happened.


             reply	other threads:[~2012-02-14  8:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14  8:10 vbyakovl23 at gmail dot com [this message]
2012-02-15  9:07 ` [Bug c++/52241] " izamyatin at gmail dot com
2012-02-15 17:09 ` paolo.carlini at oracle dot com
2012-02-16  9:01 ` vbyakovl23 at gmail dot com
2012-02-16  9:03 ` vbyakovl23 at gmail dot com
2012-02-16  9:28 ` vbyakovl23 at gmail dot com
2012-02-16  9:42 ` jakub at gcc dot gnu.org
2012-02-16 10:42 ` rguenth at gcc dot gnu.org
2012-02-16 12:29 ` jakub at gcc dot gnu.org
2012-02-16 13:46 ` paolo.carlini at oracle dot com
2012-02-16 13:47 ` paolo.carlini at oracle dot com
2012-02-16 13:55 ` paolo.carlini at oracle dot com
2012-02-16 14:04 ` paolo.carlini at oracle dot com
2012-02-16 14:04 ` paolo.carlini at oracle dot com
2012-02-16 14:14 ` jakub at gcc dot gnu.org
2012-02-16 15:15 ` paolo.carlini at oracle dot com
2012-02-19 19:14 ` izamyatin at gmail dot com
2012-02-19 19:33 ` jakub at gcc dot gnu.org
2012-02-20  8:38 ` vbyakovl23 at gmail dot com
2012-02-20  8:59 ` jakub at gcc dot gnu.org
2012-02-20 11:12 ` paolo.carlini at oracle dot com
2012-02-20 18:30 ` [Bug libstdc++/52241] " vbyakovl23 at gmail dot com
2012-02-20 21:11 ` paolo at gcc dot gnu.org
2012-02-20 21:17 ` paolo.carlini at oracle dot com
2012-02-20 21:22 ` paolo.carlini at oracle 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=bug-52241-4@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).