On Mon, 11 Dec 2023 22:41:56 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
On Mon, 11 Dec 2023 22:41:56 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
On Mon, 11 Dec 2023 22:41:56 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
On Mon, 11 Dec 2023 22:41:56 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
On Wed, 13 Dec 2023 20:51:36 GMT, Dean Long wrote:
> The man page says "no default value" but then right below describes the
> default value, which is confusing. I would remove "no default value".
This was copied from VM.cds, which pretty much does the same thing (says "no
default value" and t
On Mon, 11 Dec 2023 22:41:56 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
On Mon, 11 Dec 2023 22:41:56 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
> file name.
>
> `jcmd PID help Compiler.perfmap` shows the following usage.
>
>
> Compiler.perfmap
> Write map file for Linux perf tool.
>
> Im
On Thu, 7 Dec 2023 22:49:55 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
> file name.
>
> `jcmd PID help Compiler.perfmap` shows the following usage.
>
>
> Compiler.perfmap
> Write map file for Linux perf tool.
>
> Im
On Tue, 5 Dec 2023 20:13:11 GMT, Chris Plummer wrote:
>> Hi Chris,
>> The current design of `write_perf_map` provides a clean and explicit
>> interface. The purpose of the function is evident from its signature: to
>> write a perf map into a specified file. This explicitness makes the code
>>
On Tue, 5 Dec 2023 16:14:31 GMT, Evgeny Astigeevich
wrote:
>> src/hotspot/share/code/codeCache.cpp line 1809:
>>
>>> 1807: }
>>> 1808:
>>> 1809: void CodeCache::write_perf_map(const char* filename) {
>>
>> Why not have a `filename == nullptr` indicate that the default should be
>> used. Then
On Fri, 1 Dec 2023 21:25:19 GMT, Chris Plummer wrote:
>> Yi-Fan Tsai has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Apply man changes
>
> src/hotspot/share/code/codeCache.cpp line 1809:
>
>> 1807: }
>> 1808:
>> 1809: void CodeCache::w
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
> file name.
>
> `jcmd PID help Compiler.perfmap` shows the following usage.
>
>
> Compiler.perfmap
> Write map file for Linux perf tool.
>
> Im
On Tue, 28 Nov 2023 23:25:27 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
On Tue, 28 Nov 2023 23:25:27 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
On Tue, 28 Nov 2023 23:25:27 GMT, Yi-Fan Tsai wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
>> file name.
>>
>> `jcmd PID help Compiler.perfmap` shows the following usage.
>>
>>
>>
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
> file name.
>
> `jcmd PID help Compiler.perfmap` shows the following usage.
>
>
> Compiler.perfmap
> Write map file for Linux perf tool.
>
> Im
On Tue, 21 Nov 2023 20:42:47 GMT, Chris Plummer wrote:
>> src/jdk.jcmd/share/man/jcmd.1 line 1:
>>
>>> 1: .\" Copyright (c) 2012, 2023, Oracle and/or its affiliates. All rights
>>> reserved.
>>
>> The actual markdown source for this file needs to be updated with these
>> changes. Those source
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an optional argument for specifying a
> file name.
>
> `jcmd PID help Compiler.perfmap` shows the following usage.
>
>
> Compiler.perfmap
> Write map file for Linux perf tool.
>
> Im
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an option for specifying a file name.
>
> The help message of `jcmd PID help Compiler.perfmap` will be updated in a
> separate PR.
Yi-Fan Tsai has updated the pull request incrementall
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an option for specifying a file name.
>
> The help message of `jcmd PID help Compiler.perfmap` will be updated in a
> separate PR.
Yi-Fan Tsai has updated the pull request incrementall
On Thu, 21 Sep 2023 20:43:56 GMT, Yi-Fan Tsai wrote:
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an option for specifying a file name.
>
> The help message of Compiler.perfmap:
>
> Compiler.perfmap
> Write map file for Linux pe
On Fri, 22 Sep 2023 02:48:57 GMT, David Holmes wrote:
>> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
>> `/tmp/perf-%d.map`. This change adds an option for specifying a file name.
>>
>> The help message of Compiler.perfmap:
>>
>> Compiler.perfmap
>> Write map file for
On Thu, 21 Sep 2023 20:43:56 GMT, Yi-Fan Tsai wrote:
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an option for specifying a file name.
>
> The help message of Compiler.perfmap:
>
> Compiler.perfmap
> Write map file for Linux pe
On Thu, 21 Sep 2023 20:43:56 GMT, Yi-Fan Tsai wrote:
> `jcmd Compiler.perfmap` uses the hard-coded file name for a perf map:
> `/tmp/perf-%d.map`. This change adds an option for specifying a file name.
>
> The help message of Compiler.perfmap:
>
> Compiler.perfmap
> Write map file for Linux pe
26 matches
Mail list logo
