This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> -----Original Message----- > From: Fergus Henderson [mailto:fjh@ceres.cs.mu.OZ.AU] On > Behalf Of Fergus Henderson > Sent: 13. november 2002 07:08 > To: Casper Hornstrup > Cc: gcc-patches@gcc.gnu.org > Subject: Re: [PATCH] Fastcall support on cygwin and mingw targets > > > On 12-Nov-2002, Casper Hornstrup <chorns@users.sourceforge.net> wrote: > > > > Where/how should this check be performed? It can't be done in the > > attribute handler since all attributes may not be added to the > > attribute list yet. > > Why can't the attribute handler report an error as soon as > any two attributes conflict? Okay it can, though not as simple as: if (lookup_attribute("fastcall", TYPE_ATTRIBUTES (*node)) && lookup_attribute("stdcall", TYPE_ATTRIBUTES (*node))) { error(...) } I have added checks for conflicts with stdcall and regparm attributes. Casper Hornstrup
Attachment:
fastcall.tar.gz
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |