From: Mark Mitchell <mark@codesourcery.com>
To: Jason Merrill <jason@redhat.com>
Cc: Richard Henderson <rth@redhat.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] Simplifying TARGET_EXPR
Date: Sun, 21 Jul 2002 17:32:00 -0000 [thread overview]
Message-ID: <27410000.1027287015@warlock.codesourcery.com> (raw)
In-Reply-To: <wvly9c6ido9.fsf@prospero.cambridge.redhat.com>
--On Saturday, July 20, 2002 05:09:42 PM +0100 Jason Merrill
<jason@redhat.com> wrote:
> I'm interested in what y'all think about the second issue; it's something
> I've run into previously when thinking about expanding NEW_EXPR.
>
> One problem with (b) is that using it requires the frontend to know about
> passing by invisible reference.
I think (b) is by far better than (a).
(What I'd really like to see is the elimination of TARGET_EXPR in the
front end before we reach the optimizers and code generators. This
might miss some opportunities for elimination of copy constructors,
but, in practice, very few. And, to be honest, I'm nervous about the
compiler changing the number of objects constructed and destructed
when optimization is enabled; that makes debugging optimized code
that much harder.)
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-07-21 21:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 18:54 Jason Merrill
2002-07-21 0:41 ` Richard Henderson
2002-07-26 14:51 ` PATCH " Jason Merrill
2002-07-21 17:32 ` Mark Mitchell [this message]
2002-07-21 18:04 ` [tree-ssa] " Gabriel Dos Reis
2002-07-21 18:14 ` Mark Mitchell
2002-07-21 20:39 ` Gabriel Dos Reis
2002-07-22 8:32 ` Michael Matz
2002-07-22 12:02 ` Gabriel Dos Reis
2002-07-24 3:22 ` Mark Mitchell
2002-07-22 12:33 ` Nathan Sidwell
2002-07-22 12:53 ` Gabriel Dos Reis
2002-07-22 13:10 ` Jason Merrill
2002-07-21 22:35 ` Jason Merrill
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 9:52 Jason Merrill
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=27410000.1027287015@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=rth@redhat.com \
/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: link
Be 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).