From: Masami Hiramatsu <mhiramat@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Peter Oberparleiter <oberpar@linux.ibm.com>
Cc: "Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arnd@arndb.de
Subject: Re: linux-next: build warnings from the build of Linus' tree
Date: Tue, 28 Aug 2018 09:43:41 +0900 [thread overview]
Message-ID: <20180828094341.d20d8fbcb9dca310d44df951@kernel.org> (raw)
In-Reply-To: <20180828072333.36af4d5d@canb.auug.org.au>
Hi Stephen,
On Tue, 28 Aug 2018 07:23:33 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Masami,
>
> On Sun, 26 Aug 2018 17:10:58 +0900 Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >
> > Hmm, unfortunately, I couldn't reproduce the ".data..LPBX1" error with
> > my gcc-8.1.0 + ld-2.30 distributed at https://cdn.kernel.org/pub/tools/crosstool/.
> > Could you also try to enable CONFIG_GCOV_PROFILE_ALL=y and build the kernel?
> > If it causes similar error, it should be caused by gcov support.
>
> Using the allyesconfig as a base and disabling CONFIG_COMPILE_TESTING
> allowed me to enable COMFIG_GCOV_PROFILE_ALL, but that just generated a
> lot more messages. Some about data..Lusan sections (I think).
OK, so it sounds like GCOV kernel itself is broken with your toolchain
(native gcc-8.2.0 on ppc64?) as same as arm32.
I added Peter in loop, he is the maintainer of GCOV kernel.
Hi Peter,
I recently added a gcov profiling for ftrace, following Documentation/dev-tools/gcov.rst.
6b7dca401cb1 ("tracing: Allow gcov profiling on only ftrace subsystem")
and it caused may orphan section warnings/errors on arm and powerpc64.
We also found same error happens when CONFIG_GCOV_PROFILE_ALL=y.
So I guess GCOV kernel subsystem broken in some environment.
(cross build)
gcc-7.3.0 + ld-2.30 => arm:NG, arm64:OK, powerpc64:OK
gcc-8.1.0 + ld-2.30 => arm:NG, arm64:OK, powerpc64:OK
(native build?)
gcc-8.2.0 + ld 2.31.1 => powerpc64:NG
gcc-7.2.1 + ld 2.27 => x86-64: OK
ppc64 NG report:
https://lkml.org/lkml/2018/8/24/72
arm NG report:
https://lkml.org/lkml/2018/8/24/345
Would you know how we can fix this issue?
Thank you,
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2018-08-28 0:43 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 [this message]
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
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=20180828094341.d20d8fbcb9dca310d44df951@kernel.org \
--to=mhiramat@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=oberpar@linux.ibm.com \
--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.