public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/63500] [4.9/5 Regression] bug in debug version of std::make_move_iterator?
Date: Thu, 09 Oct 2014 18:36:00 -0000 [thread overview]
Message-ID: <bug-63500-4-n6bBxdtLfk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63500-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63500
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-10-09
Summary|bug in debug version of |[4.9/5 Regression] bug in
|std::make_move_iterator? |debug version of
| |std::make_move_iterator?
Ever confirmed|0 |1
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
Ah, no, not my fault. The debug machinery wants at some point
__addressof(*iter) but addressof wants an lvalue reference so it is not happy
with a move iterator.
Note that the error message is confusing:
error: invalid initialization of non-const reference of type
'std::unique_ptr<Foo>&' from an rvalue of type 'std::unique_ptr<Foo>'
when it is really an xvalue of type unique_ptr<Foo>&&.
next prev parent reply other threads:[~2014-10-09 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 17:13 [Bug libstdc++/63500] New: " vermaelen.wouter at gmail dot com
2014-10-09 18:17 ` [Bug libstdc++/63500] " glisse at gcc dot gnu.org
2014-10-09 18:36 ` glisse at gcc dot gnu.org [this message]
2014-10-09 18:45 ` [Bug libstdc++/63500] [4.9/5 Regression] " redi at gcc dot gnu.org
2014-10-10 20:37 ` fdumont at gcc dot gnu.org
2014-10-15 20:41 ` fdumont at gcc dot gnu.org
2015-03-11 19:54 ` 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-63500-4-n6bBxdtLfk@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).