c++/3178: Dump format for typedefs of class types is very awkward
John Wilkinson
johnw@mp-dhcp-4-40.attlabs.att.com
Wed Jun 13 13:56:00 GMT 2001
>Number: 3178
>Category: c++
>Synopsis: Dump format for typedefs of class types is very awkward
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jun 13 13:56:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: John Wilkinson
>Release: 3.0 20010416 (prerelease)
>Organization:
AT&T Research
>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:
The -fdump-translation-unit output for a program like
struct XX {int xx;};
typedef XX YY;
is very awkward. A type_decl is generated with name YY, but the indicated
type is a record_type named YY, not the expected record_type named XX. It
is true that it is possible to deduce that XX is what is really meant, since
the scope of the fields in the record_type named YY is the record_type named
XX, but this is extremely inconvenient.
>How-To-Repeat:
Compile the program above with the the -fdump-translation-unit option and
look at the first few lines of the dump.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the Gcc-bugs
mailing list