JDK-8221685 : -XX:BytecodeVerificationRemote and -XX:BytecodeVerificationLocal should be diagnostic options
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 13
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-03-29
- Updated: 2019-08-15
- Resolved: 2019-04-24
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 13 |
|---|
13 b18Fixed  |
Related Reports
|
CSR :
|
Description
Currently, -XX:BytecodeVerificationRemote and -XX:BytecodeVerificationLocal are product options. making them diagnostic would help discourage their use in favor of -Xverify.