RFR: JDK-8251470: Add a development option equivalant to OptoNoExecute to C1 compiler
Tobias Hartmann
tobias.hartmann at oracle.com
Thu Aug 13 07:00:20 UTC 2020
Hi Ogata,
isn't that what -XX:-InstallMethods [1] is supposed to accomplish? It triggers a bailout right
before Compilation::install_code, which is the same with your code.
Also, why do you need the change in javaCalls.cpp? That would also affect C2 compiled code.
Best regards,
Tobias
[1] http://hg.openjdk.java.net/jdk/jdk/file/a7c030723240/src/hotspot/share/c1/c1_globals.hpp#l292
On 12.08.20 09:48, Kazunori Ogata wrote:
> Hi,
>
> May I get review for JDK-8251470: Add a development option equivalant to
> OptoNoExecute to C1 compiler?
>
> This patch adds a development option to compile a method with C1 and print
> disassembly of the generated native code, but to skip execution of the
> generated code, in the same manner as OptoNoExecute option does in C2.
>
> Log-based debugging is useful to support a new processor. In C1, the
> existing options BailoutAfterHIR and BailoutAfterLIR can be used if
> printing HIR/LIR is sufficient. However, there is no way to print
> disassembly of the generated code because these existing options quit
> compilation before generating native code. So this issue proposes a new
> option for this purpose.
>
>
> Bug: https://bugs.openjdk.java.net/browse/JDK-8251470
> Webrev: http://cr.openjdk.java.net/~ogatak/8251470/webrev.00/
>
>
> Regards,
> Ogata
>
More information about the hotspot-compiler-dev
mailing list