public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tsoae at mail dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54521] g++ fails to call explicit constructors in the second step of copy initialization Date: Sat, 08 Sep 2012 13:25:00 -0000 [thread overview] Message-ID: <bug-54521-4-aQGmjNHwT9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54521-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54521 --- Comment #3 from Nikolka <tsoae at mail dot ru> 2012-09-08 13:25:20 UTC --- In both cases (for g++ v4.7.1 and v4.8.0) the only compiler option was -std=c++11. Nothing magical.
next prev parent reply other threads:[~2012-09-08 13:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-07 20:38 [Bug c++/54521] New: " tsoae at mail dot ru 2012-09-07 23:10 ` [Bug c++/54521] " redi at gcc dot gnu.org 2012-09-08 12:36 ` tsoae at mail dot ru 2012-09-08 13:25 ` tsoae at mail dot ru [this message] 2012-09-09 0:30 ` redi at gcc dot gnu.org 2014-10-27 9:58 ` redi at gcc dot gnu.org 2015-07-10 22:57 ` paolo at gcc dot gnu.org 2015-07-10 22:58 ` 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-54521-4-aQGmjNHwT9@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).