This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Some questions about FIELD_DECL
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: Richard Henderson <rth at redhat dot com>, Gcc Mailing List <gcc at gcc dot gnu dot org>, jsm28 at gcc dot gnu dot org
- Date: Sat, 21 May 2005 19:25:58 -0400
- Subject: Re: Some questions about FIELD_DECL
- References: <1116715395.13015.65.camel@linux.site> <m3d5rkxgjy.fsf@uniton.integrable-solutions.net>
On Sun, 2005-05-22 at 02:14 +0200, Gabriel Dos Reis wrote:
> Daniel Berlin <dberlin@dberlin.org> writes:
>
> | While moving FIELD_DECL to it's own substruct, the following questions
> | have come up. I figured one of you might know:
> |
> | 1. Do we need DECL_ASSEMBLER_NAME on FIELD_DECL? I can't think of a
> | place where we would actually try to *output* a FIELD_DECL directly, but
> | maybe i've missed something. I ask because the C frontend tests
> | decl_assembler_name on field decl, but never sets it on them.
>
>
> What happens when you have this (in C++)
>
> namespace foo {
> union {
> int baz;
> double foobar;
> } bar;
> };
>
I tried this, and it still doesn't access DECL_ASSEMBLER_NAME of
FIELD_DECL.
> ?
>
> -- Gaby