From: Christopher Li <sparse@chrisli.org>
To: Michael Stefaniuc <mstefani@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Handle __builtin_ms_va_list.
Date: Thu, 1 Oct 2009 11:41:57 -0700 [thread overview]
Message-ID: <70318cbf0910011141r78e02d78qbb7ab4f183253406@mail.gmail.com> (raw)
In-Reply-To: <20090930213456.GA502@redhat.com>
On Wed, Sep 30, 2009 at 2:34 PM, Michael Stefaniuc <mstefani@redhat.com> wrote:
> For Win64 compiles Wine does
> #ifndef __ms_va_list
> # if defined(__x86_64__) && defined (__GNUC__)
> # define __ms_va_list __builtin_ms_va_list
> # define __ms_va_start(list,arg) __builtin_ms_va_start(list,arg)
> # define __ms_va_end(list) __builtin_ms_va_end(list)
> # else
>
> Wouldn't be as bad if sparse cannot handle those but it trips over
> WINBASEAPI DWORD WINAPI FormatMessageA(DWORD,LPCVOID,DWORD,DWORD,LPSTR,DWORD,__ms_va_list*);
> WINBASEAPI DWORD WINAPI FormatMessageW(DWORD,LPCVOID,DWORD,DWORD,LPWSTR,DWORD,__ms_va_list*);
> producing this errors for basically every file:
> wine/include/winbase.h:1546:96: error: Expected ) in function declarator
> wine/include/winbase.h:1546:96: error: got *
> wine/include/winbase.h:1547:97: error: Expected ) in function declarator
> wine/include/winbase.h:1547:97: error: got *
Applied.
Thanks
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-01 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 21:34 Handle __builtin_ms_va_list Michael Stefaniuc
2009-10-01 18:41 ` Christopher Li [this message]
2009-11-25 14:15 ` Getting info from used typedef Thomas Schmid
2009-11-30 23:41 ` Christopher Li
2009-12-01 12:30 ` Antwort: " Thomas Schmid
2009-12-01 18:49 ` Christopher Li
2009-12-02 14:05 ` Thomas Schmid
2010-01-21 0:38 ` Christopher Li
2010-01-26 15:28 ` Thomas Schmid
2010-01-29 1:21 ` Christopher Li
2010-02-02 8:52 ` Thomas Schmid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70318cbf0910011141r78e02d78qbb7ab4f183253406@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mstefani@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).