public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/53657] New: [C++11] pair(pair&&) move constructor is non-trivial Date: Wed, 13 Jun 2012 14:53:00 -0000 [thread overview] Message-ID: <bug-53657-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53657 Bug #: 53657 Summary: [C++11] pair(pair&&) move constructor is non-trivial Classification: Unclassified Product: gcc Version: 4.7.1 Status: UNCONFIRMED Keywords: ABI Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: redi@gcc.gnu.org CC: paolo.carlini@oracle.com As discussed in PR 53646 the std::pair move constructor is non-trivial and so causes an unfortunate ABI change where std::pair gets returned from functions by invisible reference instead of in registers. Defaulting it makes it trivial, but causes other problems: // XXX Defaulted?!? Breaks std::map!!! pair(pair&& __p) noexcept(__and_<is_nothrow_move_constructible<_T1>, is_nothrow_move_constructible<_T2>>::value) : first(std::forward<first_type>(__p.first)), second(std::forward<second_type>(__p.second)) { }
next reply other threads:[~2012-06-13 14:53 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-13 14:53 redi at gcc dot gnu.org [this message] 2012-06-14 8:45 ` [Bug libstdc++/53657] " rguenth at gcc dot gnu.org 2012-06-14 9:15 ` redi at gcc dot gnu.org 2012-06-14 9:18 ` redi at gcc dot gnu.org 2012-06-14 9:40 ` [Bug libstdc++/53657] [4.7/4.8 Regression][C++11] " rguenth at gcc dot gnu.org 2012-06-14 9:41 ` [Bug libstdc++/53657] [C++11] " paolo.carlini at oracle dot com 2012-06-14 9:44 ` paolo.carlini at oracle dot com 2012-06-14 10:59 ` [Bug libstdc++/53657] [4.7/4.8 Regression] " redi at gcc dot gnu.org 2012-06-14 13:18 ` redi at gcc dot gnu.org 2012-06-19 9:31 ` paolo.carlini at oracle dot com 2012-06-20 15:05 ` paolo.carlini at oracle dot com 2012-06-20 15:11 ` daniel.kruegler at googlemail dot com 2012-06-20 15:16 ` paolo.carlini at oracle dot com 2012-06-20 15:21 ` redi at gcc dot gnu.org 2012-06-20 15:24 ` paolo.carlini at oracle dot com 2012-06-20 15:27 ` paolo.carlini at oracle dot com 2012-06-20 15:27 ` daniel.kruegler at googlemail dot com 2012-06-20 15:31 ` redi at gcc dot gnu.org 2012-07-13 9:05 ` paolo.carlini at oracle dot com 2012-07-13 12:39 ` bkoz at gcc dot gnu.org 2012-07-13 12:44 ` paolo.carlini at oracle dot com 2012-07-13 12:55 ` rguenther at suse dot de 2012-07-15 15:08 ` redi at gcc dot gnu.org
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-53657-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: 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).