All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Pavel Roskin <proski@gnu.org>, linux-sparse@vger.kernel.org
Subject: exposing __attribute__ portability macros in lib.h; any objections?
Date: Sun, 25 Feb 2007 14:45:29 -0800	[thread overview]
Message-ID: <45E21189.1060202@freedesktop.org> (raw)
In-Reply-To: <20070223223027.GA5671@chrisli.org>

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

Christopher Li wrote:
> Fix a bug that match_idents forget to end with NULL
[...]
> Signed-Off-By: Christopher Li <sparse@chrisli.org>
[...]
> -		if (match_idents(token, &asm_ident, &__asm_ident, &__asm___ident)) {
> +		if (match_idents(token, &asm_ident, &__asm_ident, &__asm___ident, NULL)) {

Applied.

I'd also like to apply a patch to use __attribute__((__sentinel__)) on
match_idents, which would have caught this problem.  In order to do so
portably, I plan to add a portability macro SENTINEL_ATTR, like the
FORMAT_ATTR macro currently in lib.h.  However, lib.h currently defines
FORMAT_ATTR, uses it for a few prototypes, and then undefines it.  Any
objections to defining SENTINEL_ATTR and leaving it defined (and probably
doing the same for FORMAT_ATTR)?  I don't think those would pollute the
namespace any more than lib.h already does with position, verbose, info, and
similar.

- Josh Triplett


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

  parent reply	other threads:[~2007-02-25 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 17:25 Fun with Linux 2.6.21-rc1 Pavel Roskin
2007-02-23 19:59 ` Pavel Roskin
2007-02-23 22:30   ` [PATCH] " Christopher Li
2007-02-24  1:53     ` Pavel Roskin
2007-02-25 22:45     ` Josh Triplett [this message]
2007-02-26 10:43       ` exposing __attribute__ portability macros in lib.h; any objections? Christopher Li

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=45E21189.1060202@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=sparse@chrisli.org \
    /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.