All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 0/6] dump macros definitions
Date: Thu, 6 Apr 2017 01:05:47 -0700	[thread overview]
Message-ID: <CANeU7QmfECS8w2o4M-aESz+FDU4R3ycNq0s2bzb65Zd+=XHD1g@mail.gmail.com> (raw)
In-Reply-To: <20170404214955.47926-1-luc.vanoostenryck@gmail.com>

On Tue, Apr 4, 2017 at 2:49 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> The goal of this series is to add support for GCC's -dD.
>
> This implementation is quite straightforward:
> - record all macro's name
> - dump the tokens corresponding to each macros
>   without argument expansion.
>
> This series is available at:
>         git://github.com/lucvoo/sparse.git dump-macros
> based on commit:
>         14964df5373292af78b29529d4fc7e1a26b67a97 (sparse-next @ 2017-03-31)
> up to commit:
>         9a01ec7d42d6013ead12cb111b1a1879d0c856ab

Just a heads up this week I am very occupied, don't have much
time for sparse at all. I will resume sparse hacking in the week
end. Hopefully make some progress on sparse-next.

Sorry for the delay guys.

Chris

  parent reply	other threads:[~2017-04-06  8:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 21:49 [PATCH 0/6] dump macros definitions Luc Van Oostenryck
2017-04-04 21:49 ` [PATCH 1/6] define ident_list Luc Van Oostenryck
2017-04-04 21:49 ` [PATCH 2/6] teach sparse how to dump macro definitions Luc Van Oostenryck
2017-06-01  6:56   ` Christopher Li
2017-06-01 14:08     ` Luc Van Oostenryck
2017-04-04 21:49 ` [PATCH 3/6] teach sparse how to handle -dD flag Luc Van Oostenryck
2017-04-04 21:49 ` [PATCH 4/6] let -dD report macro defintions Luc Van Oostenryck
2017-04-04 21:49 ` [PATCH 5/6] let -dD report #undef too Luc Van Oostenryck
2017-04-04 21:49 ` [PATCH 6/6] fix -dD for never-defined #undef Luc Van Oostenryck
2017-04-06  8:05 ` Christopher Li [this message]
2017-04-06 11:51   ` [PATCH 0/6] dump macros definitions Luc Van Oostenryck

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='CANeU7QmfECS8w2o4M-aESz+FDU4R3ycNq0s2bzb65Zd+=XHD1g@mail.gmail.com' \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.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.