Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: make selfcheck
Date: Mon, 17 Jul 2017 20:28:28 +0100	[thread overview]
Message-ID: <ae7e6285-eb5b-9137-fab4-0ecc502aab7a@ramsayjones.plus.com> (raw)
In-Reply-To: <CANeU7QmRaS8C8AyvtduDccK_w9pOjqppbMDoEDtyNH0OnN6ikw@mail.gmail.com>



On 17/07/17 20:16, Christopher Li wrote:
> On Mon, Jul 17, 2017 at 2:19 PM, Ramsay Jones
> <ramsay@ramsayjones.plus.com> wrote:
>>
>> This should have been './cgcc -no-compile', of course. :(
>>
> Yes, of course. I discover that myself too. I am sending out a V2
> version of the patches.
> In the V2 version I move the checker command to be controlled by "$(CHECKER)".
> For example I can change CHECKER to test-linearize and get the full
> byte code output.
> 
> BTW, are you OK I merge your change with mine in the V2 patches?

yes, no problem.

I nearly have a clean 'make selfcheck' (I suspect you do too!).
I was supposed to have gone out a while ago, ... I guess I will
not get it finished before I go. :(

ATB,
Ramsay Jones



  reply	other threads:[~2017-07-17 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 16:30 make selfcheck Ramsay Jones
2017-07-17 18:19 ` Ramsay Jones
2017-07-17 19:16   ` Christopher Li
2017-07-17 19:28     ` Ramsay Jones [this message]
2017-07-18 12:53       ` Christopher Li
2017-07-18 16:52         ` Ramsay Jones
2017-07-18 17:04           ` 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=ae7e6285-eb5b-9137-fab4-0ecc502aab7a@ramsayjones.plus.com \
    --to=ramsay@ramsayjones.plus.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --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