public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56636] strange interaction of dynamic_cast and unique_ptr Date: Wed, 20 Mar 2013 09:43:00 -0000 [thread overview] Message-ID: <bug-56636-4-WGsoRb1kiN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56636-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56636 --- Comment #3 from Paolo Carlini <paolo.carlini at oracle dot com> 2013-03-20 09:43:46 UTC --- (friendly note to Daniel: "gcc 4.8.0 trunk" doesn't make much sense ;) Either you mean trunk (future 4.9) or the recently created gcc-4_8-branch branch, from which 4.8.0 will be released. Or maybe both, I don't know)
next prev parent reply other threads:[~2013-03-20 9:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-16 16:59 [Bug c++/56636] New: " gcc-bugs at naturalcleaningcalgary dot com 2013-03-16 17:40 ` [Bug c++/56636] " redi at gcc dot gnu.org 2013-03-20 8:38 ` daniel.kruegler at googlemail dot com 2013-03-20 9:43 ` paolo.carlini at oracle dot com [this message] 2013-03-20 10:19 ` daniel.kruegler at googlemail dot com 2015-03-19 11:03 ` paolo.carlini at oracle dot com 2015-03-19 11:59 ` ktietz 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-56636-4-WGsoRb1kiN@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).