All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the kspp-gustavo tree
Date: Thu, 16 Nov 2023 18:39:03 -0600	[thread overview]
Message-ID: <202281f0-5a18-43ce-8b47-055748dd6d78@embeddedor.com> (raw)
In-Reply-To: <20231117113312.31379f74@canb.auug.org.au>




> arch/powerpc/lib/sstep.c:289:23: error: writing 8 bytes into a region of size 0 [-Werror=stringop-overflow=]
>    289 |                 up[2] = byterev_8(up[1]);
>        |                 ~~~~~~^~~~~~~~~~~~~~~~~~
> arch/powerpc/lib/sstep.c: In function 'emulate_loadstore':
> arch/powerpc/lib/sstep.c:681:11: note: at offset 16 into destination object 'u' of size 16
>    681 |         } u = {};
>        |           ^
> arch/powerpc/lib/sstep.c:681:11: note: at offset 16 into destination object 'u' of size 16
> arch/powerpc/lib/sstep.c:681:11: note: at offset 16 into destination object 'u' of size 16
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>    c94c73da81d7 ("Makefile: Enable -Wstringop-overflow globally")
> 
> I have used te kspp-gustavo tree from next-20231116 for today.
> 
I'll address those issues right away.

Thanks for the report, Stephen.
--
Gustavo




  reply	other threads:[~2023-11-17  0:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17  0:33 linux-next: build failure after merge of the kspp-gustavo tree Stephen Rothwell
2023-11-17  0:39 ` Gustavo A. R. Silva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-21  2:19 Stephen Rothwell
2023-11-21 16:31 ` Gustavo A. R. Silva
2023-11-21 23:15   ` Stephen Rothwell
2021-10-18  8:30 Stephen Rothwell
2021-10-20 16:18 ` Gustavo A. R. Silva
2021-10-20 16:20   ` Kees Cook
2021-10-25  1:55 ` Stephen Rothwell
2021-10-25 19:19   ` Kees Cook
2021-10-25 19:31     ` Gustavo A. R. Silva
2021-10-25 19:34       ` Kees Cook
2021-10-18  7:15 Stephen Rothwell
2021-10-18 17:13 ` Gustavo A. R. Silva
2021-10-25  1:54 ` Stephen Rothwell
2021-10-25  2:11   ` Gustavo A. R. Silva
2021-10-25  2:42     ` Steven Rostedt
2021-10-25  4:30       ` Stephen Rothwell
2021-10-25 11:35         ` Steven Rostedt
2021-10-14 23:48 Stephen Rothwell
2021-10-15  0:07 ` Gustavo A. R. Silva
2021-10-15  8:02   ` Stephen Rothwell
2021-09-29 23:59 Stephen Rothwell
2021-09-30  0:11 ` Gustavo A. R. Silva
2020-08-17 23:38 Stephen Rothwell
2020-08-18  0:06 ` Gustavo A. R. Silva
2020-08-17 23:34 Stephen Rothwell
2020-08-17 23:46 ` Gustavo A. R. Silva

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=202281f0-5a18-43ce-8b47-055748dd6d78@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=gustavoars@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.