stan/jdk-24
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

8309228: Clarify EXPERIMENTAL flags comment in hotspot/share/runtime/globals.hpp

Browse Source 
Reviewed-by: stuefe
This commit is contained in:
David Holmes 2023-06-20 06:43:21 +00:00
parent b2e86aef65
commit 96a7db7b3c
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/hotspot/share/runtime/globals.hpp
View File

@ -67,21 +67,22 @@
// option, you must first specify +UnlockDiagnosticVMOptions.
// (This master switch also affects the behavior of -Xprintflags.)
//
// EXPERIMENTAL flags are in support of features that are not
// part of the officially supported product, but are available
// EXPERIMENTAL flags are in support of features that may not be
// an officially supported part of a product, but may be available
// for experimenting with. They could, for example, be performance
// features that may not have undergone full or rigorous QA, but which may
// help performance in some cases and released for experimentation
// by the community of users and developers. This flag also allows one to
// be able to build a fully supported product that nonetheless also
// ships with some unsupported, lightly tested, experimental features.
// Refer to the documentation of any products using this code for details
// on support and fitness for production.
// Like the UnlockDiagnosticVMOptions flag above, there is a corresponding
// UnlockExperimentalVMOptions flag, which allows the control and
// modification of the experimental flags.
//
// Nota bene: neither diagnostic nor experimental options should be used casually,
// and they are not supported on production loads, except under explicit
// direction from support engineers.
// Refer to the documentation of any products using this code for details.
//
// MANAGEABLE flags are writeable external product flags.
// They are dynamically writeable through the JDK management interface