public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/3187] gcc lays down two copies of constructors
Date: Fri, 16 Jan 2004 18:19:00 -0000	[thread overview]
Message-ID: <20040116181955.26824.qmail@sources.redhat.com> (raw)
In-Reply-To: <20010614114602.3187.peter@empeg.com>


------- Additional Comments From mmitchel at gcc dot gnu dot org  2004-01-16 18:19 -------
I'm changing this to an enhancement request.

It is, in some sense, a regression -- but it's really a direct consequence of
the new ABI.  

Fixing it will require substantial effort.  I hope that we will get a chance to
do the multiple-entry point stuff -- but it's certainly not going to happen
before GCC 3.4.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
            Summary|[3.3/3.4 Regression] gcc    |gcc lays down two copies of
                   |lays down two copies of     |constructors
                   |constructors                |
   Target Milestone|3.4.0                       |---


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3187


  parent reply	other threads:[~2004-01-16 18:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010614114602.3187.peter@empeg.com>
2003-06-01 19:13 ` [Bug c++/3187] gcc-3.0 prerelease " pinskia@physics.uc.edu
2003-06-24  0:45 ` [Bug c++/3187] [3.3/3.4 Regression] " pinskia at physics dot uc dot edu
2003-06-24  0:50 ` pinskia at physics dot uc dot edu
2003-06-24 14:48 ` [Bug c++/3187] [3.3/3.4 Regression] gcc " bangerth at dealii dot org
2003-06-24 17:22 ` mmitchel at gcc dot gnu dot org
2003-11-25 21:42 ` gbburkhardt at aaahawk dot com
2003-11-29  1:52 ` pinskia at gcc dot gnu dot org
2004-01-12 17:12 ` bangerth at dealii dot org
2004-01-14  3:57 ` giovannibajo at libero dot it
2004-01-14  5:31 ` pinskia at gcc dot gnu dot org
2004-01-16 18:19 ` mmitchel at gcc dot gnu dot org [this message]
2004-01-18  2:45 ` [Bug c++/3187] " giovannibajo at libero dot it
2004-08-12  1:51 ` pinskia at gcc dot gnu dot org
2005-06-15 21:09 ` larue at cadence dot com
2005-06-15 21:19 ` pinskia at gcc dot gnu dot org
     [not found] <bug-3187-2475@http.gcc.gnu.org/bugzilla/>
2005-11-02  2:07 ` pinskia at gcc dot gnu dot org
2006-02-05  0:20 ` ian at airs dot com
2006-02-05  0:27   ` Andrew Pinski
2006-02-05  0:27 ` pinskia at physics dot uc dot edu
2006-02-05  0:42 ` ian at airs dot com
2006-02-05  0:55 ` pinskia at gcc dot gnu dot org
2006-02-05  3:59 ` gdr at integrable-solutions dot net
2006-02-05  4:00 ` gdr at integrable-solutions dot net
2006-09-05  7:18 ` gcc at mirality dot co dot nz
2007-05-25  3:57 ` maddox at google dot com
2008-02-19 20:21 ` jason at gcc dot gnu dot org
2008-02-25 18:37 ` jason at gcc dot gnu dot org
2008-07-29 11:32 ` dbaldin at upb dot de
2008-07-29 13:58 ` manu at gcc dot gnu dot org
2008-08-01 16:08 ` amylaar at gcc dot gnu dot org
2008-10-21 18:39 ` alexandre dot nunes at gmail dot com
2008-12-22  3:13 ` jason at gcc dot gnu dot org
2009-08-27  1:41 ` carrot at google dot com
2009-11-12  4:51 ` jason at gcc dot gnu dot org
2009-11-18  9:54 ` jakub at gcc dot gnu dot org
2009-12-01 20:10 ` jakub at gcc dot gnu dot org
2009-12-02 14:32 ` jakub at gcc dot gnu dot org
     [not found] <bug-3187-4@http.gcc.gnu.org/bugzilla/>
2012-10-18 18:01 ` ararunprasad at gmail dot com
2012-10-18 23:02 ` paolo.carlini at oracle dot com
2012-10-19  6:41 ` ararunprasad at gmail dot com
2012-10-19 10:06 ` jakub at gcc dot gnu.org
2012-10-19 10:34 ` ararunprasad at gmail dot com

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=20040116181955.26824.qmail@sources.redhat.com \
    --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: 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).