Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <017601c15465$94e266a0$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <20011014025328 DOT 24230 DOT qmail AT web14505 DOT mail DOT yahoo DOT com> <20011013232846 DOT A2364 AT redhat DOT com> Subject: Re: GCC-3 additions Date: Sun, 14 Oct 2001 14:06:20 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 14 Oct 2001 04:12:04.0191 (UTC) FILETIME=[617AA6F0:01C15466] ----- Original Message ----- From: "Christopher Faylor" To: Sent: Sunday, October 14, 2001 1:28 PM Subject: Re: GCC-3 additions > >2) How important is fastcall calling convention to cygwin apps. I have > >been working with Eric Kohl on a patchset that he is keen to get into mingw > >binaries. ReactOS project needs them for building MS-compat device drivers. > > They involve changes in binutils (as, dlltool, ld) as well as gcc. These > >are still WIP > > I'd like to have fastcall conventions. I think it is necessary if we want > gcc to be a replacement for MSVC. Also a requirement to build many low level things with gcc - and if/when we get more 'mounting' capability, a logical extension to that is the ability to provide _real_ win32 mounting - and that will require fastcall AFAIK. > Out of curiousity, how does fastcall differ from attribute ((regparm (n)))? AFAIK it's simply the symbol convention in the object file that is the issue. Rob