X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=Ro Hi6JKkjZbuvYLX7ZAgprRn4oCTPW4xHucJ1MQSI+4PrRBmwKDU9ERq9g0x4fAQCL PSWtyDDUa+rFaeLDCV9CnsYy/Xq0KeTFUaVpxwj1/RH1AzYfTA6G3kUAwVEGpXIM DfusfqyTFP+ei88vya1UPnfuaN3d9IEuAg41Ic+cw= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=H1l7q1m8 BwUO+v8kfej9YvyPHNs=; b=PN8CWA9/aYVVvK23/9Gl6dRJen9ru6vvo2eOwAkw +5xRMloCGVsav20sS8txLRdd1lj3GtdfiMASVC1U0k1kLGDMX2RYOH0+Nfro9qWi o5K04bikpyY84v0m91fGGhOoq99Bl7U92xjcs+2K6nQhVNGFlRLAyTRoix9/BClN L2A= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-qg0-f46.google.com MIME-Version: 1.0 X-Received: by 10.140.96.116 with SMTP id j107mr22294476qge.6.1393850830455; Mon, 03 Mar 2014 04:47:10 -0800 (PST) In-Reply-To: References: <5313A789 DOT 2080205 AT gmail DOT com> Date: Mon, 3 Mar 2014 13:47:10 +0100 Message-ID: Subject: Re: va_list and char* are ambiguous From: Kai Tietz To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Hi, cygwin64 shares for 64-bit the ABI of Windows native. This is caused by different reasons (eg. unwind-table description for prologue, etc). So for Windows targets va_list is indeed of 'char *' type. And this is ok. The variant of x86_64 abi, which uses indeed a structure-variant for variadic-arguments plus some call-abi extensions, isn't recommented for on Windows. If your linux code relies on structure-variadic x86_64-ABI, it seems to me broken, and needs to be ported. Hope this answers your question. Regards, Kai -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple