RFR: JDK-8027711: Unify wildcarding syntax for CompileCommand and CompileOnly [v5]
Tobias Holenstein
tholenstein at openjdk.org
Fri Jun 9 13:44:20 UTC 2023
> At the moment `CompileCommand` and `CompileOnly` use different syntax for matching methods.
>
> ### Old CompileOnly format
> - matching a **method name** with **class name** and **package name**:
> `-XX:CompileOnly=package/path/Class.method`
> `-XX:CompileOnly=package/path/Class::method`
> `-XX:CompileOnly=package.path.Class::method`
> BUT NOT `-XX:CompileOnly=package.path.Class.method`
>
> - just matching a **single method name**:
> `-XX:CompileOnly=.hashCode`
> `-XX:CompileOnly=::hashCode`
> BUT NOT `-XX:CompileOnly=hashCode`
>
> - Matching **all method names** in a **class name** with **package name**
> `-XX:CompileOnly=java/lang/String`
> BUT NOT `-XX:CompileOnly=java/lang/String.`
> BUT NOT `-XX:CompileOnly=java.lang.String`
> BUT NOT `-XX:CompileOnly=java.lang.String::` (This is actually a bug)
> BUT NOT `-XX:CompileOnly=String`
> BUT NOT `-XX:CompileOnly=String.`
> BUT NOT `-XX:CompileOnly=String::`
>
> - Matching **all method names** in a **class name** with **NO package name**
> `-XX:CompileOnly=String`
> BUT NOT `-XX:CompileOnly=String.`
> BUT NOT `-XX:CompileOnly=String::`
>
> - There is a bug when `CompileOnly` ends with `::` where the `CompileOnly` is just ignored
> e.g. `-XX:CompileOnly=String::` compiles as many methods as when omitting the `-XX:CompileOnly=` command
>
> ### CompileCommand=compileonly format
> `CompileCommand` allows two different forms for paths:
> - `package/path/Class.method`
> - `package.path.Class::method`
>
> In contrary to `CompileOnly` `CompileCommand` supports wildcard matching using `*`. `*` can appear at the beginning and/or end of a `package.path.Class` and `method` name.
>
> Valid forms:
> `-XX:CompileCommand=compileonly,*.lang.*::*shCo*`
> `-XX:CompileCommand=compileonly,*/lang/*.*shCo*`
> `-XX:CompileCommand=compileonly,java.lang.String::*`
> `-XX:CompileCommand=compileonly,*::hashCode`
> `-XX:CompileCommand=compileonly,*ng.String::hashC*`
> `-XX:CompileCommand=compileonly,*String::hash*`
>
> Invalid forms (Error: Embedded * not allowed):
> `-XX:CompileCommand=compileonly,java.*.String::has*Code`
>
> ### Use CompileCommand syntax for CompileOnly
> At the moment, in some cases it is not possible to just take pattern used with `CompileOnly` and plug it into compile command file. Syntax used by CompileOnly is also not very intuitive.
>
> `CompileOnly` is convenient because it's shorter to write and takes lists of patterns, whereas `CompileCommand` only takes one pattern per command.
>
> With this PR `CompileOnly` becomes an alias for `CompileCommand=compileonly` with possibility to take lists as ...
Tobias Holenstein has updated the pull request incrementally with one additional commit since the last revision:
Update compilerOracle.cpp
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/13802/files
- new: https://git.openjdk.org/jdk/pull/13802/files/c9ae4991..c5a7f608
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=13802&range=04
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=13802&range=03-04
Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
Patch: https://git.openjdk.org/jdk/pull/13802.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/13802/head:pull/13802
PR: https://git.openjdk.org/jdk/pull/13802
More information about the core-libs-dev
mailing list