This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC] passing C++ decimal class as underlying scalar type
- From: Janis Johnson <janis187 at us dot ibm dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Thu, 19 Nov 2009 09:13:44 -0800
- Subject: Re: [RFC] passing C++ decimal class as underlying scalar type
- References: <1255466359.5960.4.camel@janis-laptop> <4AF04B7A.2080702@redhat.com>
- Reply-to: janis187 at us dot ibm dot com
On Tue, 2009-11-03 at 10:25 -0500, Jason Merrill wrote:
> On 10/13/2009 04:39 PM, Janis Johnson wrote:
> > #define TYPE_TRANSPARENT_UNION(NODE) \
> > (UNION_TYPE_CHECK (NODE)->type.transparent_union_flag)
> >
> > +/* Indicates that objects of this type (a RECORD_TYPE) should be passed
> > + the same way that the first (and only) member would be passed. */
> > +#define TYPE_TRANSPARENT_RECORD(NODE) \
> > + (RECORD_TYPE_CHECK (NODE)->type.transparent_union_flag)
>
> The change looks good to me except that I would use the same macro for
> both RECORD_TYPE and UNION_TYPE.
Would that patch be acceptable for GCC 4.5, or should I wait?
Meanwhile the C++ ABI group hasn't addressed a patch requiring
this behavior for decimal class arguments.
Janis