From: Andi Kleen <ak@linux.intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@linux-foundation.org>,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: disabling -Wstringop-truncation
Date: Thu, 30 Aug 2018 15:32:06 -0700 [thread overview]
Message-ID: <87in3r32qh.fsf@linux.intel.com> (raw)
In-Reply-To: <20180831080714.4f94fba9@canb.auug.org.au> (Stephen Rothwell's message of "Fri, 31 Aug 2018 08:07:14 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi Linus,
>
> I am now mainly using gcc v8.2 for my builds and -Wstringop-truncation
> causes so many warnings that I am sure to miss others, so I have
> applied the below to my fixes tree until the noise reduces.
I have the same problem.
However It's not clear if they're all false positives (I suspect not)
It would be better to move the warning to W=2 or so, and also needs
someone actually looking at them.
-Andi
next prev parent reply other threads:[~2018-08-30 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 22:07 linux-next: disabling -Wstringop-truncation Stephen Rothwell
2018-08-30 22:32 ` Andi Kleen [this message]
2018-08-30 22:45 ` Stephen Rothwell
2018-08-31 1:17 ` Linus Torvalds
2018-09-20 16:28 ` Miguel Ojeda
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=87in3r32qh.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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