From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8893 invoked by alias); 12 Nov 2002 18:45:27 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 8870 invoked from network); 12 Nov 2002 18:45:22 -0000 Received: from unknown (HELO cicero1.cybercity.dk) (212.242.40.4) by sources.redhat.com with SMTP; 12 Nov 2002 18:45:22 -0000 Received: from user5.cybercity.dk (fxp0.user5.ip.cybercity.dk [212.242.41.51]) by cicero1.cybercity.dk (Postfix) with ESMTP id 4886415FC9E; Tue, 12 Nov 2002 19:45:21 +0100 (CET) Received: from CHLAPTOP (port57.ds1-trg.adsl.cybercity.dk [212.242.245.122]) by user5.cybercity.dk (Postfix) with ESMTP id C63DB1A7; Tue, 12 Nov 2002 19:45:15 +0100 (CET) From: "Casper Hornstrup" To: "'Fergus Henderson'" Cc: Subject: RE: [PATCH] Fastcall support on cygwin and mingw targets Date: Tue, 12 Nov 2002 10:45:00 -0000 Message-ID: <002e01c28a7b$9f60ffe0$0300000a@csiteoffice.csite.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <20021111192817.GA13166@ceres.cs.mu.oz.au> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-SW-Source: 2002-11/txt/msg00742.txt.bz2 > -----Original Message----- > From: Fergus Henderson [mailto:fjh@ceres.cs.mu.OZ.AU] On > Behalf Of Fergus Henderson > Sent: 11. november 2002 20:28 > To: Casper Hornstrup > Cc: gcc-patches@gcc.gnu.org > Subject: Re: [PATCH] Fastcall support on cygwin and mingw targets > > > On 11-Nov-2002, Casper Hornstrup wrote: > > > > > 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. > > > > > > > stdcall attribute after fastcall attribute - fastcall calling > > convention is used, but the symbol is prefixed with _ not @. > > > > Obviously a bug, but how should this situation be handled? Which > > attribute should win and should gcc emit a warning or error out? > > > > fastcall attribute after stdcall attribute - same result. fastcall > > attribute after regparm(3) attribute - fastcall wins. > > regparm(3) attribute after fastcall attribute - fastcall wins. > > IMHO the desirable behaviour is for gcc to report an error > in all of these cases. 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. > > > > >+ 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. > > > > I think it is a reference to fastcall only being used on > Intel Windows > > NT platforms (eg. it was not used on Windows NT/Alpha). Maybe it > > should be removed? > > Either that, or just delete the "NT". I'll delete "NT".