public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stanislav.manilov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60081] Internal compiler error: Error reporting routines re-entered. Date: Wed, 30 Apr 2014 12:29:00 -0000 [thread overview] Message-ID: <bug-60081-4-qW2M4xo1sA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60081-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60081 --- Comment #4 from Stan Manilov <stanislav.manilov at gmail dot com> --- Here is a simple way to reproduce the bug: ============================== #include <vector> #include <memory> int main() { std::vector<std::unique_ptr<int>> v; std::unique_ptr<int> px(new int (1)); v.push_back(px); } ============================== There is a bug in the code: push_back tries to copy the given element by default. This should return an error along the lines of "Call to deleted copy constructor of std::unique_ptr". Instead it gives ICE. A solution to the bug in the code is to explicitly call std::move like so: ============================== #include <vector> #include <memory> int main() { std::vector<std::unique_ptr<int>> v; std::unique_ptr<int> px(new int (1)); v.push_back(std::move(px)); } ==============================
next prev parent reply other threads:[~2014-04-30 12:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-05 16:04 [Bug c++/60081] New: " stanislav.manilov at gmail dot com 2014-03-06 20:35 ` [Bug c++/60081] " dartmetrash at gmail dot com 2014-03-06 20:37 ` dartmetrash at gmail dot com 2014-03-06 20:39 ` dartmetrash at gmail dot com 2014-04-30 12:29 ` stanislav.manilov at gmail dot com [this message] 2014-05-11 14:41 ` 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-60081-4-qW2M4xo1sA@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).