All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Michael Stefaniuc <mstefani@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Ignore the cdecl and stdcall attributes for now.
Date: Tue, 15 May 2007 23:32:27 -0700	[thread overview]
Message-ID: <464AA57B.3010205@freedesktop.org> (raw)
In-Reply-To: <20070515220536.GA23923@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Michael Stefaniuc wrote:
> Wine uses the __stdcall__ attribute extensively. The effects of the
> patch on a sparse run on the Wine code are:
> - Removes 143000 "attribute '__stdcall__': unknown attribute" errors.
> - Removes 116 "attribute '__cdecl__': unknown attribute" errors.
> - Reduces the amount of "error: too many errors" from 1992 to 1459.
> 
> Signed-off-by: Michael Stefaniuc <mstefani@redhat.com>

Applied, along with a test case.  Thanks!

I'd love to see the results you get with Wine; in particular, I'd love to see
and fix any parse errors.  Would you consider posting a build log somewhere
with latest Sparse from Git?

Did you integrate Sparse into the Wine build system, or did you use CC=cgcc?

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-05-16  6:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 22:05 Ignore the cdecl and stdcall attributes for now Michael Stefaniuc
2007-05-16  6:32 ` Josh Triplett [this message]
2007-05-16 11:19   ` Michael Stefaniuc
2007-05-16 12:46     ` Sam Ravnborg
2007-05-22 22:39     ` Josh Triplett
     [not found]   ` <46520647.9090802@redhat.com>
     [not found]     ` <4652819D.4040101@freedesktop.org>
2007-05-22 14:41       ` Michael Stefaniuc
2007-05-22 20:32         ` Josh Triplett
2007-05-22 23:44           ` Running sparse on the Wine code (Was: Re: Ignore the cdecl and stdcall attributes for now.) Michael Stefaniuc
2007-05-23  2:01             ` Josh Triplett

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=464AA57B.3010205@freedesktop.org \
    --to=josh@freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.