All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>,
	Michael Stefaniuc <mstefani@redhat.com>
Subject: Re: [PATCH 4/5] Fix an __attribute__() parsing error
Date: Tue, 22 May 2007 15:37:54 -0700	[thread overview]
Message-ID: <465370C2.3010801@freedesktop.org> (raw)
In-Reply-To: <46533263.3010108@ramsay1.demon.co.uk>

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

Ramsay Jones wrote:
> 
> When updating this patch from the 0.3 version, I made the (new) third parameter
> KW_ATTRIBUTE only, rather than (KW_ATTRIBUTE | KW_ASM), since it did not seem
> correct to allow an asm there; is that correct?

Correct; I don't think you can have an asm there.

> The test case for this was abstracted from an example in the "expat.h" header file.
> 
> $cat ape.c
> 
> typedef void (__attribute__((__cdecl__)) *FP)(void *u, const char *n);
> 
> void set_FP(void *cb, FP f);

Applied.  I think you just made a Wine developer very happy.  Michael, this
patch fixes the test case you provided for Wine; I applied your patch for the
new test case.

Thanks, Ramsay!

- Josh Triplett



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

  reply	other threads:[~2007-05-22 22:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 18:11 [PATCH 4/5] Fix an __attribute__() parsing error Ramsay Jones
2007-05-22 22:37 ` Josh Triplett [this message]
2007-05-22 23:17   ` Michael Stefaniuc
2007-05-24 17:07     ` Ramsay Jones
2007-05-24 15:27   ` Ramsay Jones

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=465370C2.3010801@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=mstefani@redhat.com \
    --cc=ramsay@ramsay1.demon.co.uk \
    /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.