This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/19159] [4.0/4.1 Regression] Undefined symbol: vtable for __cxxabiv1::__vmi_class_type_info
- From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Oct 2005 02:08:05 -0000
- Subject: [Bug c++/19159] [4.0/4.1 Regression] Undefined symbol: vtable for __cxxabiv1::__vmi_class_type_info
- References: <bug-19159-276@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #34 from mmitchel at gcc dot gnu dot org 2005-10-31 02:08 -------
According to the thread starting with the reference in Comment #31, this is
just a spurious warning on systems without weak symbols. As such, it's never
going to be release-critical.
The two leading proposals were made for resolving the problem: (1) use a
dynamic initialization on systems without weak symbols, or (2) warn only if the
static variable is actually addressed, as otherwise the fact that there are
multiple copies doesn't matter. I agree with Jason that (2) is the best
option, and it should be relatively easy to implement, given that we already
mark things as addressed; we could just move the warning to that location.
--
mmitchel at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|link-failure |diagnostic
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19159