-
Enhancement
-
Resolution: Fixed
-
P3
-
9
-
b114
-
generic
-
generic
Currently most of flags which control instrinsics generation and usage are product:
product(bool, UseAESIntrinsics, false, \
"Use intrinsics for AES versions of crypto") \
and some diagnostic:
diagnostic(ccstrlist, DisableIntrinsic, "", \
"do not expand intrinsics whose (internal) names appear here") \
By default runtime enables intrinsics on platforms which support them.
The flags are used on command line only when we need to disable intrinsics (or for testing). It is fine to convert all intrinsics flags to diagnostic.
product(bool, UseAESIntrinsics, false, \
"Use intrinsics for AES versions of crypto") \
and some diagnostic:
diagnostic(ccstrlist, DisableIntrinsic, "", \
"do not expand intrinsics whose (internal) names appear here") \
By default runtime enables intrinsics on platforms which support them.
The flags are used on command line only when we need to disable intrinsics (or for testing). It is fine to convert all intrinsics flags to diagnostic.
- relates to
-
JDK-8153655 TESTBUG: intrinsics tests must be updated to enable diagnostic options
-
- Resolved
-
-
JDK-8151779 Some intrinsic flags could be replaced with one general flag
-
- Resolved
-
-
JDK-8235981 Introduce a flag to enable JVM intrinsics
-
- Closed
-
1.
|
Remove/adapt documentation for intrinsic flags after JDK-8145348 |
|
Resolved | Clifford Wayne (Inactive) | 2017-02-24 |