All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Steven Rostedt <rostedt@goodmis.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings from the build of Linus' tree
Date: Sun, 26 Aug 2018 03:53:23 +0900	[thread overview]
Message-ID: <20180826035323.254463c8b183e6912c5b9a13@kernel.org> (raw)
In-Reply-To: <CAK8P3a0LXxq8tgsz9YL3hT47dB6nKeBdip3gFA5w0dgRGDwCMQ@mail.gmail.com>

Hi Arnd,

On Fri, 24 Aug 2018 14:46:16 +0200
Arnd Bergmann <arnd@arndb.de> wrote:

> On Fri, Aug 24, 2018 at 10:23 AM Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > On Fri, 24 Aug 2018 13:32:06 +1000
> > Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > > Hi all,
> > >
> > > After merging the origin tree, today's linux-next build (powerpc
> > > allyesconfig) produced these warnings:
> > >
> > > Maybe introduced by commit
> > >
> > >   6b7dca401cb1 ("tracing: Allow gcov profiling on only ftrace subsystem")
> > >
> > > I am guessing, but that is the only new thing that affects all of
> > > kernel/trace ...
> >
> > Yes, I agree. But I just followed Documentation/dev-tools/gcov.rst
> > to enable profiling in kernel/trace. Hmm, doesn't ppc64 support
> > GCOV_PROFILE?  (But as far as I can see, ARCH_HAS_GCOV_PROFILE_ALL
> > is enabled in arch/powerpc/Kconfig)
> >
> > Anyway, I'll try to reproduce it.
> 
> Thje same commit causes a link failure on ARM with a randconfig
> kernel (see https://pastebin.com/KspjpyKG for the .config):

OK, I confirmed that this happened with both gcc-7.3.0 and gcc-8.1.0
with your config.
I also confirmed that CONFIG_GCOV_PROFILE_ALL causes same issue.
(Note that CONFIG_GCOV_PROFILE_ALL depends on !CONFIG_COMPILE_TEST,
 so allyesconfig disables it always)

Hmm, now gcov kernel itself might have a problem on arm and 
powerpc(on gcc-8)?

Thanks,


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2018-08-25 18:53 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24  3:32 linux-next: build warnings from the build of Linus' tree Stephen Rothwell
2018-08-24  8:20 ` Masami Hiramatsu
2018-08-24 11:47   ` Masami Hiramatsu
2018-08-24 12:42     ` Stephen Rothwell
2018-08-25  1:51       ` Masami Hiramatsu
2018-08-26  8:10       ` Masami Hiramatsu
2018-08-27 21:23         ` Stephen Rothwell
2018-08-28  0:43           ` Masami Hiramatsu
2018-09-06 10:49             ` Peter Oberparleiter
2018-09-06 16:42               ` Masami Hiramatsu
2018-09-07 12:50                 ` Peter Oberparleiter
2018-09-08  3:57                   ` Masami Hiramatsu
2018-09-10 13:27                     ` Peter Oberparleiter
2018-09-11 11:49                       ` Masami Hiramatsu
2018-09-11 14:10                         ` Masami Hiramatsu
2018-09-06 22:14               ` Stephen Rothwell
2018-09-07  3:34                 ` Stephen Rothwell
2018-10-11  0:48               ` Stephen Rothwell
2018-10-11  7:44                 ` Peter Oberparleiter
2018-10-11  9:58                   ` Stephen Rothwell
2018-10-11  9:58                     ` Stephen Rothwell
2018-10-11 10:37                     ` Greg KH
2018-10-11 11:09                       ` Peter Oberparleiter
2018-10-11 13:54                       ` Arnd Bergmann
2018-10-11 22:12                         ` [GIT PULL] A couple of warning fixes Stephen Rothwell
2018-10-12 10:51                           ` Greg KH
2018-08-24 12:46   ` linux-next: build warnings from the build of Linus' tree Arnd Bergmann
2018-08-25 18:53     ` Masami Hiramatsu [this message]
2018-08-25 19:53       ` Arnd Bergmann
2018-09-01  9:50         ` Masami Hiramatsu
2018-09-01 12:38           ` [PATCH] ARM: linker script: GCOV kernel may refers data in __exit Masami Hiramatsu
2018-09-01 12:38             ` Masami Hiramatsu
2018-09-11 14:12             ` Masami Hiramatsu
2018-09-11 14:12               ` Masami Hiramatsu
2018-08-29  2:11     ` linux-next: build warnings from the build of Linus' tree Greentime Hu

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=20180826035323.254463c8b183e6912c5b9a13@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rostedt@goodmis.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.