From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Nick Gasson <nick.gasson@arm.com>
Cc: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] perf jvmti: Fix demangling Java symbols
Date: Wed, 27 May 2020 19:34:05 -0300 [thread overview]
Message-ID: <20200527223405.GE16490@kernel.org> (raw)
In-Reply-To: <20200527162300.GD16490@kernel.org>
Em Wed, May 27, 2020 at 01:23:00PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, May 27, 2020 at 11:20:57AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Mon, Apr 27, 2020 at 02:15:16PM +0800, Nick Gasson escreveu:
> > > For a Java method signature like:
> > >
> > > Ljava/lang/AbstractStringBuilder;appendChars(Ljava/lang/String;II)V
> > >
> > > The demangler produces:
> > >
> > > void class java.lang.AbstractStringBuilder.appendChars(class java.lang., shorttring., int, int)
> > >
> > > The arguments should be (java.lang.String, int, int) but the demangler
> > > interprets the "S" in String as the type code for "short". Correct this
> > > and two other minor things:
> > >
> > > - There is no "bool" type in Java, should be "boolean".
> > >
> > > - The demangler prepends "class" to every Java class name. This is not
> > > standard Java syntax and it wastes a lot of horizontal space if the
> > > signature is long. Remove this as there isn't any ambiguity between
> > > class names and primitives.
> > >
> > > Also added a test case.
> >
> > So, I took this and split into a patch for the new 'perf test java' and
> > then the fix, so that we can see the problem being detected and then
> > apply the fix and see it fixed, the last patch in this series thus
> > became:
>
> This is in my tmp.perf/core branch pending a round of testing, after
> that it'll move to perf/core on its way to 5.8, thanks.
All tests passed, moved to perf/core.
- Arnaldo
next prev parent reply other threads:[~2020-05-27 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 6:15 [PATCH 0/3] perf jvmti: Various fixes to JVMTI agent Nick Gasson
2020-04-27 6:15 ` [PATCH 1/3] perf jvmti: Fix jitdump for methods without debug info Nick Gasson
2020-05-14 22:06 ` Ian Rogers
2020-04-27 6:15 ` [PATCH 2/3] perf jvmti: Do not report error when missing debug information Nick Gasson
2020-05-14 22:08 ` Ian Rogers
2020-05-27 14:07 ` Arnaldo Carvalho de Melo
2020-05-27 14:08 ` Arnaldo Carvalho de Melo
2020-04-27 6:15 ` [PATCH 3/3] perf jvmti: Fix demangling Java symbols Nick Gasson
2020-05-14 22:09 ` Ian Rogers
2020-05-27 14:10 ` Arnaldo Carvalho de Melo
2020-05-27 14:20 ` Arnaldo Carvalho de Melo
2020-05-27 16:23 ` Arnaldo Carvalho de Melo
2020-05-27 22:34 ` Arnaldo Carvalho de Melo [this message]
2020-05-28 5:42 ` Nick Gasson
2020-04-27 10:35 ` [PATCH 0/3] perf jvmti: Various fixes to JVMTI agent Jiri Olsa
2020-05-14 8:56 ` Nick Gasson
2020-05-14 13:23 ` Arnaldo Carvalho de Melo
2020-05-14 22:41 ` Ian Rogers
2020-05-15 7:45 ` Nick Gasson
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=20200527223405.GE16490@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nick.gasson@arm.com \
--cc=peterz@infradead.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).