This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/41172] C frontend botches type.name for typedef chains
- From: "dwitte at mozilla dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Aug 2009 05:52:52 -0000
- Subject: [Bug c/41172] C frontend botches type.name for typedef chains
- References: <bug-41172-6148@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #6 from dwitte at mozilla dot com 2009-08-26 05:52 -------
Well, if it's comparing two existing types, sure. :)
How does it work in the case where the parser is dealing with the declaration
|bar_t func()|, and it wants to determine if it's seen the declaration of
|bar_t| before?
Wait, don't tell me. The parser keeps a separate mapping of names->trees?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41172