On Thu, 16 Jul 2026 09:49:12 GMT, Guanqiang Han <[email protected]> wrote:
> Please review this change, thanks! > > **Description:** > > Some VM long options only accept arguments in the `--option=value` form, even > though the launcher help states that long-option arguments may also be > separated by whitespace. As a result, options such as > `--illegal-final-field-mutation debug`, `--illegal-native-access warn` are > not parsed correctly. > > **Solution:** > > Add `IsNonModuleVMWhiteSpaceOption()` to identify VM long options that accept > whitespace-separated arguments and convert them to the `--option=value` form > before passing them to the VM. Add `--enable-final-field-mutation` to the > existing module-option handling. Normalize missing arguments for other VM > long options to `--option=` so that they can be handled by the existing > option validation logic. > > **Test:** > > GHA > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). This pull request has now been integrated. Changeset: aa8af371 Author: Guanqiang Han <[email protected]> Committer: Brent Christian <[email protected]> URL: https://git.openjdk.org/jdk/commit/aa8af37164be6072a496f9e4ddd00bfe8d9ef95a Stats: 238 lines in 6 files changed: 151 ins; 1 del; 86 mod 8387729: Not all --long-options accept space as seperator Reviewed-by: alanb ------------- PR: https://git.openjdk.org/jdk/pull/31928
