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]

Re: [PATCH] Fastcall support on cygwin and mingw targets

From: Christopher Faylor <cgf at redhat dot com>
To: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
Cc: Casper Hornstrup <chorns at users dot sourceforge dot net>, gcc-patches at gcc dot gnu dot org
Date: Sun, 10 Nov 2002 22:10:10 -0500
Subject: Re: [PATCH] Fastcall support on cygwin and mingw targets
References: <3DC0BC2C.2070007@twcny.rr.com> <004801c288d4$a5a58e50$0300000a@csiteoffice.csite.com> <20021111015042.GA1711@ceres.cs.mu.oz.au>

On Mon, Nov 11, 2002 at 12:50:42PM +1100, Fergus Henderson wrote:
>Some comments above the definition of ASM_OUTPUT_LABELREF would be nice.
>
>What happens if a function has multiple attributes,
>e.g. both fastcall and stdcall or both fastcall and regparm(3)?
>It may be worth adding a test for that case.
>
>>+ The @code{fastcall} calling convention exists in Windows NT for Intel
>>+ processors only.
>
>That part of the documentation is wrong.
>Cygwin and Mingw work on most variants of Windows, not just Windows NT.

Fastcall does work on any version of Windows, AFAIK.

cgf

References:
- [PATCH] Fastcall support on cygwin and mingw targets
  - From: Casper Hornstrup
- Re: [PATCH] Fastcall support on cygwin and mingw targets
  - From: Fergus Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]