public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "meisenmann.lba@fh-salzburg.ac.at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65189] New: Malformed (C++) class-hierarchy dump on abstract class (in comparission to GCC 4.6.x)
Date: Tue, 24 Feb 2015 11:33:00 -0000	[thread overview]
Message-ID: <bug-65189-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65189

            Bug ID: 65189
           Summary: Malformed (C++) class-hierarchy dump on abstract class
                    (in comparission to GCC 4.6.x)
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: meisenmann.lba@fh-salzburg.ac.at

Following minimal sample (Ie. test.cpp) does generate a noticeable different
class-hierarchy dump with GCC 4.9.2 - compared to GCC 4.6.4:

class A
{
public:
 virtual ~A();
 virtual int getVal() const = 0;
};

Calling
 gcc -c -fdump-classhierarchy test.cpp && type test.cpp.002t.class

a) generates with GCC 4.6.4 (as expected):

Vtable for A
A::_ZTV1A: 5u entries
0   (int (*)(...))0
4   (int (*)(...))(& _ZTI1A)
8   (int (*)(...))A::~A
12  (int (*)(...))A::~A
16  (int (*)(...))__cxa_pure_virtual

Class A .. dropped; Ie. no difference

b) with GCC 4.9.2, the output is

A::_ZTV1A: 5u entries
0   (int (*)(...))0
4   (int (*)(...))(& _ZTI1A)
8   (int (*)(...))0u
12  (int (*)(...))0u
16  (int (*)(...))__cxa_pure_virtual

The two d'tor-entries (offset 8 and 12) are 0u ?!

This issue also affects the generated dump with option
"-fdump-translation-unit"
... which is used by the ABI Compliance Checker (ABICC).
For example, if I compare the ABI-compatibility of abstract classes between
different GCC-versions, a incorrect/false-positive mismatch of the vtable
(concerning the virtual d'tor entries) is determined.

I've already tested some additional options to dtermine a work-around, but
without luck!

Best regards from Salzburg,
Markus


             reply	other threads:[~2015-02-24 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 11:33 meisenmann.lba@fh-salzburg.ac.at [this message]
2015-02-24 12:49 ` [Bug c++/65189] " jakub at gcc dot gnu.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=bug-65189-4@http.gcc.gnu.org/bugzilla/ \
    --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).