public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/20408] Unnecessary code generated for empty structs Date: Fri, 12 Feb 2021 02:30:16 +0000 [thread overview] Message-ID: <bug-20408-4-c1xSLMR6pf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-20408-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20408 --- Comment #25 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:031e97207463710797625382baff112b6c3ade51 commit r10-9362-g031e97207463710797625382baff112b6c3ade51 Author: Jason Merrill <jason@redhat.com> Date: Mon Feb 8 17:04:03 2021 -0500 c++: generic lambda, fn* conv, empty class [PR98326] Here, in the thunk returned from the captureless lambda conversion to pointer-to-function, we try to pass through invisible reference parameters by reference, without doing a copy. The empty class copy optimization was messing that up. gcc/cp/ChangeLog: PR c++/98326 PR c++/20408 * cp-gimplify.c (simple_empty_class_p): Don't touch an invisiref parm. gcc/testsuite/ChangeLog: PR c++/98326 * g++.dg/cpp1y/lambda-generic-empty1.C: New test.
next prev parent reply other threads:[~2021-02-12 2:30 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20408-4@http.gcc.gnu.org/bugzilla/> 2020-12-09 13:53 ` jason at gcc dot gnu.org 2021-02-09 1:52 ` cvs-commit at gcc dot gnu.org 2021-02-12 2:30 ` cvs-commit at gcc dot gnu.org [this message] [not found] <bug-20408-9525@http.gcc.gnu.org/bugzilla/> 2007-11-26 14:17 ` steven at gcc dot gnu dot org 2007-11-27 9:40 ` rguenth at gcc dot gnu dot org 2005-03-10 15:48 [Bug middle-end/20408] New: Unnessasary " chris at bubblescope dot net 2005-03-10 17:31 ` [Bug middle-end/20408] Unnecessary " pinskia at gcc dot gnu dot org 2005-03-10 17:35 ` pinskia at gcc dot gnu dot org 2005-09-04 16:26 ` rguenth at gcc dot gnu dot org 2005-09-04 16:37 ` rguenth at gcc dot gnu dot org 2005-09-04 17:12 ` rguenth at gcc dot gnu dot org 2005-09-05 10:36 ` rguenth at gcc dot gnu dot org 2005-09-05 10:48 ` rguenth at gcc dot gnu dot org 2005-09-05 12:38 ` rguenth at gcc dot gnu dot 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-20408-4-c1xSLMR6pf@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).