linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] cleanup write to argument array hack
Date: Mon, 04 Dec 2006 23:37:37 -0800	[thread overview]
Message-ID: <457521C1.4060102@freedesktop.org> (raw)
In-Reply-To: <20061130101136.GA27500@chrisli.org>

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

Christopher Li wrote:
> The sparse interface is a kind of snaky that it change the input argument
> array. The function sparse() does the same hack just to skip the files.
> 
> This patch add the ptr list for string. So sparse_initialize will
> return list of file to compile. The string pointer is not aligned
> at word boundary. This patch introduce non taged version of the ptr
> list iteration function.

Nice improvement; thanks.

Since tagged lists seem like by far the common case, I'd prefer to see
PTR_ENTRY keep its current name, as you did with add_ptr_list.  Also, your
patch didn't update test-unssa.c.  I've merged your patch, with those two
additional changes.

I'd also love to see some additional static type checking here, to prevent
using the untagged functions on a tagged list or vice versa at compile time,
rather than allowing mysterious corruption at runtime.

- Josh Triplett


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

      reply	other threads:[~2006-12-05  7:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 10:11 [PATCH] cleanup write to argument array hack Christopher Li
2006-12-05  7:37 ` Josh Triplett [this message]

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=457521C1.4060102@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=linux-sparse@vger.kernel.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 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).