public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: peter@empeg.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/3187: gcc-3.0 prerelease lays down two copies of constructors
Date: Thu, 14 Jun 2001 11:46:00 -0000 [thread overview]
Message-ID: <20010614183839.26949.qmail@sourceware.cygnus.com> (raw)
>Number: 3187
>Category: c++
>Synopsis: gcc-3.0 prerelease lays down two copies of constructors
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Thu Jun 14 11:46:02 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Peter Hartley
>Release: gcc version 3.0 20010614 (prerelease)
>Organization:
>Environment:
PC Linux host, ARM Linux cross-compiler
Configured with: ../gcc/configure --prefix=/home/peter --host=i686-linux --build=i686-linux --target=arm-cvs-linux --enable-languages=c,c++ --enable-static
>Description:
Two (sometimes three) identical copies of constructors and destructors are laid down. The linker doesn't fail this, but the binaries produced are 20% bigger (on our real-world example) than necessary.
>How-To-Repeat:
arm-cvs-linux-g++ -S aubergine.cpp -o aubergine2.s
The aubergine2.s file clearly contains two identical constructors and two identical destructors.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-14 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 11:46 peter [this message]
2001-06-14 12:16 Philip Blundell
2001-06-15 0:53 nathan
2003-02-19 15:06 Steven Bosscher
2003-02-19 15:26 Nathan Sidwell
2003-02-19 15:26 Steven Bosscher
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=20010614183839.26949.qmail@sourceware.cygnus.com \
--to=peter@empeg.com \
--cc=gcc-gnats@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).