From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
clang-built-linux <llvm@lists.linux.dev>
Subject: Re: linux-next: Tree for Jul 14
Date: Sun, 17 Jul 2022 23:05:04 +0100 [thread overview]
Message-ID: <CADVatmONHx5KjODAXWjKDs6OayDr2HJQpP6_mR+xSAADX_eByw@mail.gmail.com> (raw)
In-Reply-To: <YtCJeieW4Mz1VfRx@dev-arch.thelio-3990X>
Hi Nathan,
On Thu, Jul 14, 2022 at 10:24 PM Nathan Chancellor <nathan@kernel.org> wrote:
>
> Dropping the next list and Stephen as these issues are likely present on
> mainline as well.
>
> On Thu, Jul 14, 2022 at 07:26:27PM +0100, Sudip Mukherjee wrote:
> > Hi Nathan,
> >
> > On Thu, Jul 14, 2022 at 5:29 PM Nathan Chancellor <nathan@kernel.org> wrote:
> > >
> > > On Thu, Jul 14, 2022 at 05:21:32PM +0100, Sudip Mukherjee wrote:
> > > > Hi Nathan,
> > > >
> > > > On Thu, Jul 14, 2022 at 5:05 PM Nathan Chancellor <nathan@kernel.org> wrote:
> > > > >
> > > > > Hi Sudip,
> > > > >
> > > > > On Thu, Jul 14, 2022 at 12:07:06PM +0100, Sudip Mukherjee (Codethink) wrote:
> > > > > > Hi Stephen,
> > > > > >
> > > > > > On Thu, Jul 14, 2022 at 06:55:14PM +1000, Stephen Rothwell wrote:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Changes since 20220713:
> > > > > >
> > > > > > Build failures on next-20220714:
> > > > >
> > > > > <snip>
> > > > >
> >
> > <snip>
> >
> > >
> > > Sure! I am not sure that we have tested mips or powerpc allmodconfig now
> > > that I am thinking about it but we'll certainly take a look at any
> > > issues that come from them and see what we can do.
> >
> > The build errors from powerpc allmodconfig with clang:
>
> Thanks for testing!
>
> > 1)
> > Error: External symbol 'memset' referenced from prom_init.c
>
> Good to know this is not clang specific.
Ok, so clang is also trying to use memset for any array.
Linus suggested adding volatile. ref:
https://lore.kernel.org/lkml/CAHk-=whc3Uvhrmrr27xp5=oOhSDjXc5s1ZxC3B7xMYV6oj4WRQ@mail.gmail.com/
for the gcc-12 problem, and with that I can see that clang has worked
as expected and removed memset from struct prom_args. But now memset
is still there for other arrays in prom_init_mem() and others. I think
we will still need a patch for clang, and that will also work when the
gcc-12 bug is fixed.
--
Regards
Sudip
next prev parent reply other threads:[~2022-07-17 22:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 8:55 linux-next: Tree for Jul 14 Stephen Rothwell
2022-07-14 11:07 ` Sudip Mukherjee (Codethink)
2022-07-14 16:05 ` Nathan Chancellor
2022-07-14 16:21 ` Sudip Mukherjee
2022-07-14 16:29 ` Nathan Chancellor
2022-07-14 16:55 ` Sudip Mukherjee
2022-07-14 18:26 ` Sudip Mukherjee
2022-07-14 21:24 ` Nathan Chancellor
2022-07-15 22:06 ` Sudip Mukherjee
2022-07-17 22:05 ` Sudip Mukherjee [this message]
2022-07-14 18:51 ` Nick Desaulniers
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 4:15 Stephen Rothwell
2021-07-14 3:25 Stephen Rothwell
2020-07-14 10:03 Stephen Rothwell
2017-07-14 3:58 Stephen Rothwell
2016-07-14 6:18 Stephen Rothwell
2015-07-14 5:41 Stephen Rothwell
2014-07-14 7:17 Stephen Rothwell
2014-07-14 17:50 ` Nick Krause
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=CADVatmONHx5KjODAXWjKDs6OayDr2HJQpP6_mR+xSAADX_eByw@mail.gmail.com \
--to=sudipm.mukherjee@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.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;
as well as URLs for NNTP newsgroup(s).