public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67302] [C++14] copy elision in return (expression) Date: Tue, 30 Jun 2020 14:13:15 +0000 [thread overview] Message-ID: <bug-67302-4-7AhMM7vDcx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67302-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67302 Antony Polukhin <antoshkka at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antoshkka at gmail dot com --- Comment #3 from Antony Polukhin <antoshkka at gmail dot com> --- Can reproduce with GCC 10.1 https://godbolt.org/z/tYvccG
next prev parent reply other threads:[~2020-06-30 14:13 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-21 7:06 [Bug c++/67302] New: " osensei80 at gmail dot com 2015-08-21 10:31 ` [Bug c++/67302] " redi at gcc dot gnu.org 2015-08-21 10:43 ` [Bug c++/67302] [C++14] " redi at gcc dot gnu.org 2020-06-30 14:13 ` antoshkka at gmail dot com [this message] 2021-06-19 19:39 ` ppalka at gcc dot gnu.org 2021-06-21 11:56 ` cvs-commit at gcc dot gnu.org 2021-06-21 12:00 ` ppalka 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-67302-4-7AhMM7vDcx@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).