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++/19159] [4.0 Regression] Undefined symbol: vtable for __cxxabiv1::__vmi_class_type_info
Date: Thu, 06 Jan 2005 23:05:00 -0000 [thread overview]
Message-ID: <20050106230456.29992.qmail@sourceware.org> (raw)
In-Reply-To: <20041226162616.19159.danglin@gcc.gnu.org>
------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2005-01-06 23:04 -------
Subject: Re: [4.0 Regression] Undefined symbol: vtable for __c
> Dave, would you mind testing with this revision to the patch?
I'll try this evening. It's taken some time but I believe that the
following change broke my original suggested fix to decl2.c
(import_export_decl):
2004-12-16 Nathan Sidwell <nathan@codesourcery.com>
PR c++/18905
* cp-tree.h (integral_constant_value): Declare.
* call.c (null_ptr_cst_p): Use integral_constant_value, not
decl_constant_value.
(convert_like_real): Likewise.
* class.c (check_bitfield_decl): Likewise.
* cvt.c (ocp_convert): Likewise.
(convert): Remove unnecessary decl_constant_value call.
* decl.c (compute_array_index_type): Use integral_constant_value,
not decl_constant_value.
(build_enumerator): Likewise.
* decl2.c (grokfield): Likewise.
* init.c (decl_constant_value): Simplify.
(integral_constant_value): New.
* pt.c (fold_decl_constant_value): Use integral_constant_value,
remove subsequent check.
(tsubst): Use integral_constant_value, not decl_constant_value.
(tsubst_copy, unify): Likewise.
* typeck.c (decay_conversion): Likewise.
(build_compound_expr): Remove unnecessary decl_constant_value
calls.
(build_static_cast_1, build_reinterpret_cast_1):
(convert_for_assignment): Remove comment about not calling
decl_constant_value.
I know the breakage occurred between 12/16/04 00:00:00 UTC and 12/17/04
00:00:00 UTC. I was going to try your previous changes prior to the point
of the breakage. Let me know if you can see why the above might have
affected the situation.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19159
next prev parent reply other threads:[~2005-01-06 23:05 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 16:26 [Bug c++/19159] New: " 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 [this message]
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
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
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=20050106230456.29992.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).