All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] sparse v0.6.4 regression
Date: Tue, 28 Sep 2021 00:41:27 +0100	[thread overview]
Message-ID: <c29182d4-3141-83c6-21f6-d7f368b3d3c5@ramsayjones.plus.com> (raw)


Hi Luc,

I noticed a regression introduced by commit a69f8d70 which, effectively,
disables the 'memcpy-max-count' check. (I had done a 'make CC=cgcc' in
git, expecting to see some warnings, including the 'memcpy-max-count'
check, and it didn't appear ... :( ). Sorry for not noticing before, but
the 'sparse' make target is supposed to suppress that warning for the
pack-revindex.c file, so ... ;P

[I tried finding your last 'kernel sparse warnings change' list email
to see how many of these warnings still appear in the kernel ... well
it would be zero with v0.6.4!]

I also included the 'case label' patch I sent before, this time with
a commit message and a test. (The test could be extended when sparse
is updated to include the full label-positioning of C23!).

ATB,
Ramsay Jones

Ramsay Jones (2):
  sparse: fix broken 'memcpy-max-count' check
  parse: warn about a 'case label' on empty statement

 parse.c                        |  5 +++++
 sparse.c                       |  2 +-
 validation/byte-count-max.c    | 28 ++++++++++++++++++++++++++++
 validation/label-positioning.c | 22 ++++++++++++++++++++++
 4 files changed, 56 insertions(+), 1 deletion(-)
 create mode 100644 validation/byte-count-max.c
 create mode 100644 validation/label-positioning.c

-- 
2.33.0

             reply	other threads:[~2021-09-27 23:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 23:41 Ramsay Jones [this message]
2022-05-21  9:44 ` [PATCH 0/2] sparse v0.6.4 regression Luc Van Oostenryck
2022-05-22 15:06   ` 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=c29182d4-3141-83c6-21f6-d7f368b3d3c5@ramsayjones.plus.com \
    --to=ramsay@ramsayjones.plus.com \
    --cc=gitster@pobox.com \
    --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.