public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9143: 64BIT: Error in dump class hiearchy file generated for basic inheritance
Date: Fri, 03 Jan 2003 10:46:00 -0000 [thread overview]
Message-ID: <20030103104602.11890.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/9143; it has been noted by GNATS.
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: michaelw@ca.ibm.com, lei@ca.ibm.com, gcc-gnats@gcc.gnu.org,
gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/9143: 64BIT: Error in dump class hiearchy file generated for basic inheritance
Date: Fri, 3 Jan 2003 11:38:13 +0100
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9143
The following mail form Janis about this PR got accidentally picked up
by GNATS as a new PR. Let's hope that this mail makes it into the audit
trail of the right PR.
Is the generated code incorrect also, or just the dump
output?
GCC generates the same dump information as that reported in
the PR for a powerpc64-linux cross compiler built from the
current mainline and from the 3.3 branch.
With a native powerpc64-linux compiler I get:
Vtable for B
B::_ZTV1B: 7 entries
0 8
8 0
16 &_ZTI1B
24 0
32 0fffffff8
40 &_ZTI1B
48 A::f()
With a native 32-bit compiler on a powerpc64-linux system
I get:
Vtable for B
B::_ZTV1B: 7 entries
0 4
4 0
8 &_ZTI1B
12 0
16 4294967292
20 &_ZTI1B
24 A::f()
For comparison purposes I got the same dumps for two other
targets. With the mainline from 20021210 on ia64-linux:
9143.C:1: sorry, unimplemented: `fdesc_expr' not supported
by dump_expr
9143.C:1: sorry, unimplemented: `fdesc_expr' not supported
by dump_expr
9143.C:5: sorry, unimplemented: `fdesc_expr' not supported
by dump_expr
9143.C:5: sorry, unimplemented: `fdesc_expr' not supported
by dump_expr
I didn't look into this, but it suggests that perhaps some
of the dump functionality used by the cross compiler isn't
supported.
With the mainline from 20021220 on i686-linux:
Vtable for B
B::_ZTV1B: 7 entries
0 4
4 0
8 &_ZTI1B
12 0
16 0fffffffc
20 &_ZTI1B
24 A::f()
This information might be useful for someone who understands
vtable layout and the dump functions.
next reply other threads:[~2003-01-03 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 10:46 Christian Ehrhardt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-02 19:46 lei
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=20030103104602.11890.qmail@sources.redhat.com \
--to=ehrhardt@mathematik.uni-ulm.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).