public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	peter@empeg.com
Subject: Re: c++/3187: gcc-3.0 prerelease lays down two copies of constructors
Date: Fri, 15 Jun 2001 00:53:00 -0000	[thread overview]
Message-ID: <20010615075306.2074.qmail@sourceware.cygnus.com> (raw)

Synopsis: gcc-3.0 prerelease lays down two copies of constructors

State-Changed-From-To: open->analyzed
State-Changed-By: nathan
State-Changed-When: Fri Jun 15 00:53:06 2001
State-Changed-Why:
    This is not a bug, however, it is a pessimization.
    The following ctor/dtors are (sometimes) required
    1) complete object ctor/dtor
    2) base object ctor/dtor
    3) new/delete ctor/dtor
    in the general case 1 & 2 are different, but for many
    classes they are the same. We should do something about
    that.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3187&database=gcc


             reply	other threads:[~2001-06-15  0:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-15  0:53 nathan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-19 15:26 Steven Bosscher
2003-02-19 15:26 Nathan Sidwell
2003-02-19 15:06 Steven Bosscher
2001-06-14 12:16 Philip Blundell
2001-06-14 11:46 peter

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=20010615075306.2074.qmail@sourceware.cygnus.com \
    --to=nathan@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=peter@empeg.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).