From: Steven Rostedt <rostedt@goodmis.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linuxppc-dev@lists.ozlabs.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v3 3/4] powerpc/kbuild: Use flags variables rather than overriding LD/CC/AS
Date: Tue, 15 May 2018 10:43:24 -0400 [thread overview]
Message-ID: <20180515104324.5230d827@gandalf.local.home> (raw)
In-Reply-To: <87tvr9o5iy.fsf@concordia.ellerman.id.au>
On Tue, 15 May 2018 15:24:21 +1000
Michael Ellerman <mpe@ellerman.id.au> wrote:
> > Have you tried building all current archs with function tracing enabled
> > to make sure this doesn't break any of them? I can do it if you want.
>
> We shouldn't need to should we? This is only touching powerpc specific
> code (if I understand perl that is).
>
> eg:
>
> $ git diff -U9 scripts/recordmcount.pl
Thanks for the added context!
Yeah, I don't look at that code much anymore since I mainly deal with
recordmcount.c now-a-days. I wonder if someone should port ppc to that.
It is also no my todo list to merge that with objtool.
Anyway,
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
> diff --git a/scripts/recordmcount.pl b/scripts/recordmcount.pl
> index 191eb949d52c..3c67304a7425 100755
> --- a/scripts/recordmcount.pl
> +++ b/scripts/recordmcount.pl
> @@ -268,18 +268,25 @@ if ($arch eq "x86_64") {
> } elsif ($arch eq "powerpc") {
> $local_regex = "^[0-9a-fA-F]+\\s+t\\s+(\\.?\\S+)";
> # See comment in the sparc64 section for why we use '\w'.
> $function_regex = "^([0-9a-fA-F]+)\\s+<(\\.?\\w*?)>:";
> $mcount_regex = "^\\s*([0-9a-fA-F]+):.*\\s\\.?_mcount\$";
>
> if ($bits == 64) {
> $type = ".quad";
> }
> + if ($endian eq "big") {
> + $cc .= " -mbig-endian ";
> + $ld .= " -EB ";
> + } else {
> + $cc .= " -mlittle-endian ";
> + $ld .= " -EL ";
> + }
>
> } elsif ($arch eq "arm") {
> $alignment = 2;
> $section_type = '%progbits';
> $mcount_regex = "^\\s*([0-9a-fA-F]+):\\s*R_ARM_(CALL|PC24|THM_CALL)" .
> "\\s+(__gnu_mcount_nc|mcount)\$";
>
> } elsif ($arch eq "arm64") {
> $alignment = 3;
>
>
> cheers
next prev parent reply other threads:[~2018-05-15 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 3:52 [PATCH v3 0/4] powerpc patches for new Kconfig language Nicholas Piggin
2018-05-14 3:52 ` [PATCH v3 1/4] powerpc/kbuild: set default generic machine type for 32-bit compile Nicholas Piggin
2018-05-14 3:52 ` [PATCH v3 2/4] powerpc/kbuild: remove CROSS32 defines from top level powerpc Makefile Nicholas Piggin
2018-05-14 3:52 ` [PATCH v3 3/4] powerpc/kbuild: Use flags variables rather than overriding LD/CC/AS Nicholas Piggin
2018-05-14 15:28 ` Steven Rostedt
2018-05-15 5:24 ` Michael Ellerman
2018-05-15 6:16 ` Nicholas Piggin
2018-05-15 14:43 ` Steven Rostedt [this message]
2018-05-16 2:37 ` Michael Ellerman
2018-05-14 3:52 ` [PATCH v3 4/4] powerpc/kbuild: move -mprofile-kernel check to Kconfig Nicholas Piggin
2018-05-14 7:42 ` kbuild test robot
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=20180515104324.5230d827@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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).