8328272: [AIX] Use flag kind "diagnostic" for platform specific flags
Reviewed-by: mdoerr, stuefe
This commit is contained in:
parent
e669d14d47
commit
b334a8e5fc
@ -45,7 +45,7 @@
|
||||
/* via shmctl). */ \
|
||||
/* Per default we quit with an error if that variable is found; for certain */ \
|
||||
/* customer scenarios, we may want to be able to run despite that variable. */ \
|
||||
product(bool, AllowExtshm, false, \
|
||||
product(bool, AllowExtshm, false, DIAGNOSTIC, \
|
||||
"Allow VM to run with EXTSHM=ON.") \
|
||||
\
|
||||
/* Maximum expected size of the data segment. That correlates with the */ \
|
||||
@ -59,17 +59,17 @@
|
||||
"Maximum expected Data Segment Size.") \
|
||||
\
|
||||
/* Use optimized addresses for the polling page. */ \
|
||||
product(bool, OptimizePollingPageLocation, true, \
|
||||
product(bool, OptimizePollingPageLocation, true, DIAGNOSTIC, \
|
||||
"Optimize the location of the polling page used for Safepoints") \
|
||||
\
|
||||
/* Use 64K pages for virtual memory (shmat). */ \
|
||||
product(bool, Use64KPages, true, \
|
||||
product(bool, Use64KPages, true, DIAGNOSTIC, \
|
||||
"Use 64K pages if available.") \
|
||||
\
|
||||
/* Normally AIX commits memory on touch, but sometimes it is helpful to have */ \
|
||||
/* explicit commit behaviour. This flag, if true, causes the VM to touch */ \
|
||||
/* memory on os::commit_memory() (which normally is a noop). */ \
|
||||
product(bool, UseExplicitCommit, false, \
|
||||
product(bool, UseExplicitCommit, false, DIAGNOSTIC, \
|
||||
"Explicit commit for virtual memory.")
|
||||
|
||||
// end of RUNTIME_OS_FLAGS
|
||||
|
Loading…
Reference in New Issue
Block a user