public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52241] Performance degradation of 447.dealII on corei7 at spec2006_base32. Date: Thu, 16 Feb 2012 09:42:00 -0000 [thread overview] Message-ID: <bug-52241-4-ncJh2Tfzkc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52241-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52241 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-16 09:26:58 UTC --- The fact that -fPIC code is often slower than -fno-pic code on many targets isn't that surprising. But libstdc++.so.6's tree.cc has been compiled with -fPIC -DPIC before Benjamin's change and is compiled with those flags after those changes as well (on x86_64 you would likely not being able to link libstdc++.so.6 otherwise). So, are you linking libstdc++ statically into the benchmark? Why? That isn't what people normally do, nor they should be doing. It is true that libstdc++.a now contains PIC code after the move to the convenience libraries, while previously it contained non-PIC code (with the exception of libsupc++ stuff that was PIC already before those changes).
next prev parent reply other threads:[~2012-02-16 9:28 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-14 8:10 [Bug c++/52241] New: " vbyakovl23 at gmail dot com 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 [this message] 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-ncJh2Tfzkc@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).