From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Chris Li <sparse@chrisli.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/3] -Wmemcpy-max-count & friends
Date: Fri, 2 Jun 2017 02:26:16 +0200 [thread overview]
Message-ID: <CAMHZB6Fd4Z2ofZJUHbN_52VRGcg__2rN9WEvb3MbHC9wduPjOA@mail.gmail.com> (raw)
In-Reply-To: <ecc76f93-d919-449d-62ff-d2f1b4bc0fae@ramsayjones.plus.com>
On Fri, Jun 2, 2017 at 2:11 AM, Ramsay Jones
<ramsay@ramsayjones.plus.com> wrote:
>
>
> On 01/06/17 21:27, Luc Van Oostenryck wrote:
>> sparse will warn if memcpy() (and some others memcpy-like
>> functions) is called with a very large static byte count.
>> But this warning cannot be disabled and the limit is arbitrary
>> fixed at 100000.
>>
>> The goal of this series is to allow to disable this warning if
>> found too unconvenient or to allow to configure its limit.
>>
>>
>> The series can also be found on the tree:
>> git://github.com/lucvoo/sparse.git memcpy-max-count
>
> Heh, I think you know I wrote a similar patch about a decade ago ...
>
> [I tried to find it the other day but couldn't find it - I think
> it is on my old laptop, which doesn't get booted up these days!]
More or less, yes. I saw it in the email where you and Junio talked
about how this memset() warning was a bit blocking for git to use
sparse, which is the motivation of these 3 patches.
-- Luc
next prev parent reply other threads:[~2017-06-02 0:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84e547c2-8a5b-225c-1363-361e091821f4@ramsayjones.plus.com>
2017-06-01 20:27 ` [PATCH 0/3] -Wmemcpy-max-count & friends Luc Van Oostenryck
2017-06-01 20:27 ` [PATCH 1/3] memcpy()'s byte count is unsigned Luc Van Oostenryck
2017-06-02 0:16 ` Ramsay Jones
2017-06-02 1:17 ` Luc Van Oostenryck
2017-06-01 20:27 ` [PATCH 2/3] add support for -Wmemcpy-max-count Luc Van Oostenryck
2017-06-02 0:23 ` Ramsay Jones
2017-06-02 0:33 ` Luc Van Oostenryck
2017-06-01 20:27 ` [PATCH 3/3] add support for -fmemcpy-max-count Luc Van Oostenryck
2017-06-02 0:30 ` Ramsay Jones
2017-06-02 0:37 ` Ramsay Jones
2017-06-02 0:38 ` Luc Van Oostenryck
2017-06-02 1:42 ` Ramsay Jones
2017-06-02 1:45 ` Luc Van Oostenryck
2017-06-02 0:11 ` [PATCH 0/3] -Wmemcpy-max-count & friends Ramsay Jones
2017-06-02 0:26 ` Luc Van Oostenryck [this message]
2017-06-03 7:47 Luc Van Oostenryck
2017-06-03 13:23 ` Ramsay Jones
2017-06-06 1:39 ` 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=CAMHZB6Fd4Z2ofZJUHbN_52VRGcg__2rN9WEvb3MbHC9wduPjOA@mail.gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=gitster@pobox.com \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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;
as well as URLs for NNTP newsgroup(s).