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++/19159] [4.0/4.1 Regression] Undefined symbol: vtable for __cxxabiv1::__vmi_class_type_info
Date: Tue, 05 Apr 2005 06:49:00 -0000 [thread overview]
Message-ID: <20050405064953.22665.qmail@sourceware.org> (raw)
In-Reply-To: <20041226162616.19159.danglin@gcc.gnu.org>
------- Additional Comments From mmitchel at gcc dot gnu dot org 2005-04-05 06:49 -------
Dave --
I suspect that there is some PCH involvement here. In particular, the warnings
you're seeing while compiling header_cassert are very surprising, in that the
preprocessed source for that file does not contain the string "_S_do_it". So, I
think the problem is related to PCH. To fix that, I'll need a test case that I
can reproduce in a cross environment; i.e., preprocessed source that I can turn
into a PCH, and then some use of the PCH that produces the warnings.
In any case, I'm going to test, and then check in, the latest patch, as lots of
link-time warnings is better than link failures.
-- Mark
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19159
next prev parent reply other threads:[~2005-04-05 6:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 16:26 [Bug c++/19159] New: [4.0 " danglin at gcc dot gnu dot org
2004-12-26 17:18 ` [Bug c++/19159] " pinskia at gcc dot gnu dot org
2004-12-27 19:14 ` mmitchel at gcc dot gnu dot org
2004-12-27 20:42 ` dave at hiauly1 dot hia dot nrc dot ca
2004-12-27 20:48 ` pinskia at gcc dot gnu dot org
2004-12-28 21:38 ` danglin at gcc dot gnu dot org
2005-01-06 23:05 ` dave at hiauly1 dot hia dot nrc dot ca
2005-01-07 7:58 ` mmitchel at gcc dot gnu dot org
2005-01-07 8:18 ` mark at codesourcery dot com
2005-01-08 22:57 ` danglin at gcc dot gnu dot org
2005-01-09 0:44 ` danglin at gcc dot gnu dot org
2005-04-01 6:23 ` [Bug c++/19159] [4.0/4.1 " mmitchel at gcc dot gnu dot org
2005-04-02 15:47 ` danglin at gcc dot gnu dot org
2005-04-04 1:26 ` mmitchel at gcc dot gnu dot org
2005-04-04 1:30 ` mmitchel at gcc dot gnu dot org
2005-04-04 1:58 ` gdr at integrable-solutions dot net
2005-04-04 2:13 ` dave at hiauly1 dot hia dot nrc dot ca
2005-04-04 3:07 ` dave at hiauly1 dot hia dot nrc dot ca
2005-04-04 3:21 ` dave at hiauly1 dot hia dot nrc dot ca
2005-04-05 6:39 ` mmitchel at gcc dot gnu dot org
2005-04-05 6:49 ` mmitchel at gcc dot gnu dot org [this message]
2005-04-05 12:07 ` dave at hiauly1 dot hia dot nrc dot ca
2005-04-05 15:20 ` mark at codesourcery dot com
2005-04-05 15:40 ` cvs-commit at gcc dot gnu dot org
2005-04-05 15:46 ` mmitchel at gcc dot gnu dot org
2005-04-05 16:30 ` pinskia at gcc dot gnu dot org
2005-04-06 2:15 ` dave at hiauly1 dot hia dot nrc dot ca
2005-04-17 4:31 ` mmitchel at gcc dot gnu dot org
2005-04-17 4:57 ` mmitchel at gcc dot gnu dot org
2005-04-29 12:22 ` pinskia at gcc dot gnu dot org
2005-07-06 16:53 ` mmitchel at gcc dot gnu dot org
2005-09-27 16:15 ` mmitchel at gcc dot gnu dot org
[not found] <bug-19159-276@http.gcc.gnu.org/bugzilla/>
2005-10-31 2:08 ` mmitchel 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=20050405064953.22665.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).