From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Wenyu Huang <huangwenyu5@huawei.com>,
pmladek@suse.com, rostedt@goodmis.org
Cc: andriy.shevchenko@linux.intel.com, linux@rasmusvillemoes.dk,
senozhatsky@chromium.org, akpm@linux-foundation.org,
linux-next@vger.kernel.org, gustavoars@kernel.org
Subject: Re: [PATCH next] Fix the build failed caused by -Wstringop-overflow
Date: Thu, 30 Nov 2023 09:52:42 -0600 [thread overview]
Message-ID: <730544ae-1e7f-4622-b986-839f81e60384@embeddedor.com> (raw)
In-Reply-To: <20231130105741.2849670-1-huangwenyu5@huawei.com>
On 11/30/23 04:57, Wenyu Huang wrote:
> gcc version: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
>
> I use this version of gcc to compile, and the compilation fails. It said
> that "error: writing 1 byte into a region of size 0
> [-Werror=stringop-overflow=]".
>
> This patch is to fix it to build successfully.
>
This doesn't really fix anything. GCC 11 is buggy and the issues you
see are false positives that doesn't show up in other versions of
the compiler.
> Fixes: 89741e7e42f6 ("Makefile: Enable -Wstringop-overflow globally")
The commit ID is from a patch that's currently in linux-next, which
does not guarantee it's a stable commit. So, it shouldn't be used
for any tag in any changelog text. In fact, it has changed a couple
of times in the last couple of weeks.
-Wstringop-overflow will soon be disabled for GCC 11 by default. So,
this patch is unnecessary. I'll probably commit a patch for this next
week. :)
Thanks
--
Gustavo
next prev parent reply other threads:[~2023-11-30 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 10:57 [PATCH next] Fix the build failed caused by -Wstringop-overflow Wenyu Huang
2023-11-30 15:52 ` Gustavo A. R. Silva [this message]
2023-11-30 17:48 ` Andy Shevchenko
2023-11-30 17:50 ` Andy Shevchenko
2023-11-30 18:04 ` Gustavo A. R. Silva
2023-11-30 18:06 ` Andy Shevchenko
2023-11-30 18:13 ` Gustavo A. R. Silva
2023-11-30 21:23 ` Andrew Morton
2023-11-30 17:56 ` Gustavo A. R. Silva
2023-11-30 18:05 ` Andy Shevchenko
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=730544ae-1e7f-4622-b986-839f81e60384@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gustavoars@kernel.org \
--cc=huangwenyu5@huawei.com \
--cc=linux-next@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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