public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14607] [3.3 Regression] Duplicate symbol "vtable for node" in files div.o and env.o
Date: Fri, 11 Jun 2004 22:40:00 -0000 [thread overview]
Message-ID: <20040611224038.13614.qmail@sourceware.org> (raw)
In-Reply-To: <20040316171907.14607.danglin@gcc.gnu.org>
------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2004-06-11 22:40 -------
Subject: Re: [3.3 Regression] Duplicate symbol "vtable for nod
> What |Removed |Added
> ----------------------------------------------------------------------------
> Target Milestone|3.3.4 |3.3.5
I'm not sure this milestone is reasonable. I did quite a bit
of investigation on this problem and came to the conclusion that
on targets that don't support one-only semantics we are more or
less scuppered by the C++ "ABI" used by GCC.
I have been testing a fix using the support for COMDAT that's
present in the hpux 10.20 linker to implement one-only support.
If I go ahead with this fix on [3.3/3.4], the new libstdc++
library will not be compatible with the previously installed
libraries. I also note that using COMDAT instead on secondary
definition symbols (as in hpux 11) will make programs compiled
under hpux 10.20 incompatible with hpux 11. As a result, any
existing old binaries will need recompilation and linking. On
the other hand, C++ is more or less broken for any non trivial
programs at the moment. So, implementing one-only support
would be a significant improvement.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14607
next prev parent reply other threads:[~2004-06-11 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 17:19 [Bug c++/14607] New: " danglin at gcc dot gnu dot org
2004-03-16 17:48 ` [Bug c++/14607] " pinskia at gcc dot gnu dot org
2004-06-11 22:22 ` pinskia at gcc dot gnu dot org
2004-06-11 22:40 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2004-06-11 22:45 ` Andrew Pinski
2004-06-11 22:45 ` pinskia at physics dot uc dot edu
2004-06-11 22:52 ` dave at hiauly1 dot hia dot nrc dot ca
2004-07-20 19:52 ` cvs-commit at gcc dot gnu dot org
2004-07-20 22:10 ` pinskia at gcc dot gnu dot org
2004-08-15 4:14 ` pinskia at gcc dot gnu dot org
2004-12-28 4:51 ` cvs-commit at gcc dot gnu dot org
2004-12-28 5:29 ` pinskia at gcc dot gnu dot org
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=20040611224038.13614.qmail@sourceware.org \
--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).