Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] pre-process: fix a compiler array subscript type warning
Date: Sat, 6 Jun 2020 01:09:53 +0200	[thread overview]
Message-ID: <20200605230953.oe5pfjmpuvkxdkl3@ltop.local> (raw)
In-Reply-To: <fbb9ba2b-14fa-c6e1-a730-80d35547ea52@ramsayjones.plus.com>

On Fri, Jun 05, 2020 at 10:29:24PM +0100, Ramsay Jones wrote:
> Hi Luc,
> 
> Having not done so in a while, last night I updated my cygwin
> installation. This resulted in updates to the versions of the
> libc/headers/gcc, among other things. (eg. gcc is now v9.3.0).
> 
> This patch fixes the new compiler warning that results!

Nice catch! I really hate the spec of these functions.

Thanks,
-- Luc

      reply	other threads:[~2020-06-05 23:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 21:29 [PATCH] pre-process: fix a compiler array subscript type warning Ramsay Jones
2020-06-05 23:09 ` Luc Van Oostenryck [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=20200605230953.oe5pfjmpuvkxdkl3@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ramsay@ramsayjones.plus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox