From: Gabriel Dos Reis <gdr@codesourcery.com>
To: Michael Matz <matz@suse.de>
Cc: Mark Mitchell <mark@codesourcery.com>,
aj@suse.de, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] Simplifying TARGET_EXPR
Date: Mon, 22 Jul 2002 12:02:00 -0000 [thread overview]
Message-ID: <m31y9wc8i9.fsf@soliton.integrable-solutions.net> (raw)
In-Reply-To: Michael Matz's message of "Mon, 22 Jul 2002 11:24:39 +0200 (CEST)"
Michael Matz <matz@suse.de> writes:
| Hi,
|
| On Sun, 21 Jul 2002, Mark Mitchell wrote:
|
| > > Do you think we should always elide copy-constructors by default,
| > > unless explicitly told the contrary?
| >
| > Yes.
| >
| > Maybe I'm developing an unhealthy paranoia.
|
| And your coworkers too it seems ;-)
If you have something particular with me, let's take it to private mails.
| First, I think you meant debugging in general, not specifically with gdb,
| didn't you? Because with -O2 programs are not debuggable easily with gdb,
| even right now,
Not just because it is already uneasy means we should make it more
difficult.
| so gdb-debugging should not be the reason to not elide
| copy ctors (or more generally debugging with programs interpreting the
| debug info). Then it can only be a form of printf debugging, or asserts.
Nobody (neither Mark nor me) is proposing not to elide copy
constructors. On the contrary, we're proposing to always elide them
unless explicitly told otherwise.
-- Gaby
next prev parent reply other threads:[~2002-07-22 11:24 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 ` [tree-ssa] " Mark Mitchell
2002-07-21 18:04 ` 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 [this message]
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=m31y9wc8i9.fsf@soliton.integrable-solutions.net \
--to=gdr@codesourcery.com \
--cc=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=matz@suse.de \
/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).