public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "J.W.Rogers+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52745] New: GCC4.7 vector uses copy instead of move constructor
Date: Tue, 27 Mar 2012 23:06:00 -0000	[thread overview]
Message-ID: <bug-52745-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52745
           Summary: GCC4.7 vector uses copy instead of move constructor
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: J.W.Rogers+gcc@gmail.com


Using GCC 4.7.0, vector seems to prefer copy rather than move when resizing.

The following program produces different (and I think incorrect) results under
GCC 4.7.0 vs GCC 4.6.1

#include <iostream>
#include <vector>

struct Stuff
{
    Stuff( ) { }
    Stuff( Stuff&& o ) { std::cout << "Move" << std::endl; }
    Stuff( const Stuff& o ) { std::cout << "Copy" << std::endl; }
};


int main( const int argc, const char** argv )
{

    std::vector< Stuff > stuff;
    std::cout << "1" << std::endl;
    stuff.push_back( Stuff() );
    std::cout << "2" << std::endl;
    stuff.push_back( Stuff() );
    std::cout << "3" << std::endl;
    stuff.push_back( Stuff() );
}

Here is the output under GCC 4.6.1

jonathan@grindserv:~$ g++-4.6.1 -std=c++0x test.cpp
jonathan@grindserv:~$ ./a.out
1
Move
2
Move
Move
3
Move
Move
Move


Here is the output under GCC 4.7.0

jonathan@grindserv:~$ g++-4.7.0 -std=c++0x test.cpp
jonathan@grindserv:~$ ./a.out
1
Move
2
Move
Copy
3
Move
Copy
Copy


             reply	other threads:[~2012-03-27 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 23:06 J.W.Rogers+gcc at gmail dot com [this message]
2012-03-27 23:13 ` [Bug libstdc++/52745] " paolo.carlini at oracle dot com
2012-03-27 23:20 ` J.W.Rogers+gcc at gmail dot com
2012-03-27 23:26 ` paolo.carlini at oracle dot com
2012-03-27 23:30 ` J.W.Rogers+gcc at gmail dot com
2012-03-27 23:42 ` paolo.carlini at oracle dot com
2012-03-28  0:12 ` paolo.carlini at oracle dot com
2012-03-28  0:22 ` J.W.Rogers+gcc 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=bug-52745-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).