From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the kspp-gustavo tree
Date: Tue, 21 Nov 2023 22:04:17 -0600 [thread overview]
Message-ID: <7e58f7a0-440f-4067-87e2-381f05bfce2b@embeddedor.com> (raw)
In-Reply-To: <20231122144814.649823ac@canb.auug.org.au>
On 11/21/23 21:48, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kspp-gustavo tree, today's linux-next build (sparc64
> defconfig) produced these warnings:
>
[..]
> mm/mempolicy.c:2890:26: note: destination object 'str' of size [0, 9223372036854775807]
> mm/mempolicy.c:2890:26: note: destination object 'str' of size [0, 9223372036854775807]
> mm/mempolicy.c:3007:26: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 3007 | *--flags = '=';
> | ~~~~~~~~~^~~~~
> mm/mempolicy.c:2890:26: note: destination object 'str' of size [0, 9223372036854775807]
> 2890 | int mpol_parse_str(char *str, struct mempolicy **mpol)
> | ~~~~~~^~~
>
> This is using gcc v11.1.0
>
This doesn't show up with more recent compilers because it was an issue in GCC.
--
Gustavo
next prev parent reply other threads:[~2023-11-22 4:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 3:48 linux-next: build warnings after merge of the kspp-gustavo tree Stephen Rothwell
2023-11-22 4:04 ` Gustavo A. R. Silva [this message]
2023-11-22 5:15 ` Stephen Rothwell
[not found] ` <bbde1882-9124-408c-9f59-de3de66bfc56@embeddedor.com>
2023-11-24 19:07 ` Gustavo A. R. Silva
2023-11-22 4:51 ` Aithal, Srikanth
2023-11-24 1:23 ` Gustavo A. R. Silva
2023-11-27 22:13 ` Stephen Rothwell
2023-11-28 21:11 ` Gustavo A. R. Silva
2023-11-30 21:54 ` Gustavo A. R. Silva
2023-11-30 22:10 ` Stephen Rothwell
2023-12-01 8:40 ` Aithal, Srikanth
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=7e58f7a0-440f-4067-87e2-381f05bfce2b@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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