public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@redhat.com>
To: Devang Patel <dpatel@apple.com>
Cc: Daniel Jacobowitz <drow@false.org>,
	Jason Molenda <jason-gcclist@molenda.com>,
	GCC Development <gcc@gcc.gnu.org>
Subject: Re: Reducing debug info for C++ ctors/dtors
Date: Wed, 13 Jul 2005 18:45:00 -0000	[thread overview]
Message-ID: <1121280286.3224.19.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <1B44CDEB-BB23-4B74-8B13-73CEE6CF0732@apple.com>


> What do others think about this patch? If people think, it is OK
> to have one additional knob for users then I'll test and submit
> formal patch.
> 
> I'll treat silence as, this idea is not OK for FSF GCC. I'd like to
> give Jason and our customers compiler with such fix ASAP. And if
> it is considered good idea for FSF GCC then I'd like to iron out
> small details (e.g. name of switch, stabs specific or general for
> all dbg format etc..), in the beginning.

I think it's useful, probably in the same vein as the
-feliminate-dwarf-dup etc switches. Probably should use the same type of
naming convention too.

-eric

  reply	other threads:[~2005-07-13 18:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12  0:37 Devang Patel
2005-07-12  0:56 ` Daniel Jacobowitz
2005-07-12  1:12   ` Jason Molenda
2005-07-12  1:18     ` Daniel Jacobowitz
2005-07-12  3:46       ` Jason Molenda
2005-07-13 18:42       ` Devang Patel
2005-07-13 18:45         ` Eric Christopher [this message]
2005-07-13 19:36           ` Mike Stump
2005-07-13 19:39             ` Eric Christopher
2005-07-13 21:05               ` Mike Stump
2005-07-13 22:11                 ` Eric Christopher

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=1121280286.3224.19.camel@dzur.sfbay.redhat.com \
    --to=echristo@redhat.com \
    --cc=dpatel@apple.com \
    --cc=drow@false.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jason-gcclist@molenda.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).