This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: New hook for custom-mangling of C++ scalars
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: Ziemowit Laski <zlaski at apple dot com>, gcc-patches at gcc dot gnu dot org
- Date: 21 Mar 2004 03:34:54 +0100
- Subject: Re: PATCH: New hook for custom-mangling of C++ scalars
- Organization: Integrable Solutions
- References: <15B7EDB0-6CA4-11D8-AF47-000393673036@apple.com><87brmrkk21.fsf@egil.codesourcery.com>
Zack Weinberg <zack@codesourcery.com> writes:
| > + if (type == bool_char_type_node) return "U6__boolc";
| > + if (type == bool_short_type_node) return "U6__bools";
| > + if (type == pixel_type_node) return "u7__pixel";
| > + if (type == bool_int_type_node) return "U6__booli";
|
| Encoding "bool X" as a "vendor-extended type qualifier" is a little
| weird, IMHO, but I don't have a problem with it. They demangle to
| "<type> __bool" (owing to the weird C++ convention of writing type
| qualifiers after the base type, contrary to English, but never mind) --
I can't make sense of that. Would you mind elaborating?
| the only way this is relevant to you is, the C++ parser had better
| accept "int __bool" as well as "__bool int".
type specifiers can appear in any order, so that should noe be a problem.
(still, "__bool int" and "int __bool" are curious notions).
-- Gaby