This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
c++/2778: -fdump-translation-unit option inaccuracies
- To: gcc-gnats at gcc dot gnu dot org
- Subject: c++/2778: -fdump-translation-unit option inaccuracies
- From: John Wilkinson <johnw at mp-dhcp-4-40 dot attlabs dot att dot com>
- Date: Tue, 8 May 2001 10:51:29 -0400
>Number: 2778
>Category: c++
>Synopsis: dump always reports base classes public
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue May 08 11:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: John Wilkinson
>Release: 3.0 20010416 (prerelease)
>Organization:
att researh
>Environment:
System: Linux mp-dhcp-4-40.attlabs.att.com 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT 2000 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc/configure
>Description:
(1) When using the -fdump-translation-unit option, the dump shows all base
classes as public, even when explicitly declared private or protected.
(2) There is no clear way to distinguish in the dump between a virtual and a
non-virtual function.
>How-To-Repeat:
The following program illustrates the base class problem:
class base {};
class derived: private base {};
And this program illustrates the virtual function problem:
struct XX {
virtual void foo();
};
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: