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: Fri, 24 Nov 2023 13:07:55 -0600 [thread overview]
Message-ID: <b3c99290-40bc-426f-b3d2-1aa903f95c4e@embeddedor.com> (raw)
In-Reply-To: <bbde1882-9124-408c-9f59-de3de66bfc56@embeddedor.com>
Hi Stephen,
On 11/22/23 00:24, Gustavo A. R. Silva wrote:
> Stephen,
>
> I need to double-check that. I'll be able to come back to work on this in 12-15 hours. I'm about to travel.
>
> Thanks
> --
> Gustavo
>
>
> On Nov 21, 2023, 23:15, at 23:15, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> Hi Gustavo,
>>
>> On Tue, 21 Nov 2023 22:04:17 -0600 "Gustavo A. R. Silva"
>> <gustavo@embeddedor.com> wrote:
>>>
>>> This doesn't show up with more recent compilers because it was an
>> issue in GCC.
>>
>> Sure, but we do still support gcc back to v5.1 .. are there other
>> earlier versions where you may want to suppress these warnings?
The GCC bug only appears in GCC 11. We should catch and fix -Wstringop-overflow
warnings with the rest of the versions that support this compiler option. :)
Thanks!
--
Gustavo
next prev parent reply other threads:[~2023-11-24 19:08 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
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 [this message]
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=b3c99290-40bc-426f-b3d2-1aa903f95c4e@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;
as well as URLs for NNTP newsgroup(s).