public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/25977] [4.1/4.2 Regression] RSO vs NRV (twice) Date: Fri, 03 Feb 2006 21:56:00 -0000 [thread overview] Message-ID: <20060203215611.25748.qmail@sourceware.org> (raw) In-Reply-To: <bug-25977-12049@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from jason at gcc dot gnu dot org 2006-02-03 21:56 ------- Subject: Bug 25977 Author: jason Date: Fri Feb 3 21:56:03 2006 New Revision: 110564 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=110564 Log: PR c++/25979 * gimplify.c (gimplify_modify_expr_rhs): Disable *& optimization for now. PR middle-end/25977 * gimplify.c (gimplify_modify_expr_rhs): It's not always safe to do RVO on the return slot if it's an NRV. Added: branches/gcc-4_1-branch/gcc/testsuite/g++.dg/opt/nrv10.C branches/gcc-4_1-branch/gcc/testsuite/g++.dg/opt/nrv11.C Modified: branches/gcc-4_1-branch/gcc/ChangeLog branches/gcc-4_1-branch/gcc/gimplify.c branches/gcc-4_1-branch/gcc/testsuite/g++.dg/opt/temp1.C -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25977
next prev parent reply other threads:[~2006-02-03 21:56 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-26 15:40 [Bug middle-end/25977] New: miscompile with classes without copy constructor mueller at gcc dot gnu dot org 2006-01-26 15:40 ` [Bug middle-end/25977] " mueller at gcc dot gnu dot org 2006-01-26 15:45 ` pinskia at gcc dot gnu dot org 2006-01-26 15:48 ` [Bug middle-end/25977] [4.1/4.2 Regression] RSO vs NRV (twice) pinskia at gcc dot gnu dot org 2006-01-26 15:50 ` pinskia at gcc dot gnu dot org 2006-01-26 15:54 ` pinskia at gcc dot gnu dot org 2006-01-26 17:36 ` pinskia at gcc dot gnu dot org 2006-01-27 16:50 ` jason at gcc dot gnu dot org 2006-02-01 3:01 ` mmitchel at gcc dot gnu dot org 2006-02-03 21:56 ` jason at gcc dot gnu dot org [this message] 2006-02-03 21:57 ` jason at gcc dot gnu dot org 2006-02-03 21:58 ` jason at gcc dot gnu dot org 2006-02-05 9:48 ` jakub 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=20060203215611.25748.qmail@sourceware.org \ --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).