public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mutz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/60621] New: std::vector::emplace_back generates massively more code than push_back
Date: Sat, 22 Mar 2014 23:32:00 -0000	[thread overview]
Message-ID: <bug-60621-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60621
           Summary: std::vector::emplace_back generates massively more
                    code than push_back
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mutz at kde dot org

Created attachment 32429
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32429&action=edit
Source of the programme used to generate the mentioned numbers

Compiling the attached program on Linux AMD64 with the following command lines:

    $ g++ -O2 -std=c++11 -o emplace-vs-push_back{.pb,.cpp}
    $ g++ -O2 -std=c++11 -o emplace-vs-push_back{.eb,.cpp} -DEMPLACE_BACK

and stripping the resulting executables:

    $ strip emplace-vs-push_back.*

I get the following sizes:

    $ size emplace-vs-push_back.*
       text    data     bss     dec     hex filename
       5570     696      40    6306    18a2 emplace-vs-push_back.eb
       4338     672      40    5050    13ba emplace-vs-push_back.pb

IOW: the emplace_back version generates roughly 1K more text (code).

This is surprising, since functionally, emplace_back is the same as
push_back(S&&), except that it saves one move ctor and one dtor call due to
in-place construction. This should result in _less_ code generated, not more.

   $ g++ -v
   Using built-in specs.
   COLLECT_GCC=g++
   COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper
   Target: x86_64-linux-gnu
   Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5'
--with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs
--enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.7 --enable-shared --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object
--enable-plugin --enable-objc-gc --with-arch-32=i586 --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
   Thread model: posix
   gcc version 4.7.2 (Debian 4.7.2-5)


             reply	other threads:[~2014-03-22 23:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 23:32 mutz at kde dot org [this message]
2014-03-23  8:24 ` [Bug libstdc++/60621] " glisse at gcc dot gnu.org
2014-03-23 11:26 ` marc at kdab dot com
2015-02-11 11:13 ` marc at kdab 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-60621-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).