JDK-8316930 : HotSpot should use noexcept instead of throw()
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: other
  • Priority: P4
  • Status: In Progress
  • Resolution: Unresolved
  • Submitted: 2023-09-26
  • Updated: 2024-07-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.
Other
tbdUnresolved
Related Reports
Blocks :  
JDK-8255082 - HotSpot Style Guide should permit noexcept
Relates :  
JDK-8305590 - Remove nothrow exception specifications from operator new
Description
throw() has been deprecated since C++11 alongside dynamic exception specifications, we should replace all instances of it with noexcept to prepare HotSpot for later versions of C++
Comments
It looks like there are a fair number of unnecessary nothrow exception specifications. Maybe they should be removed first. JDK-8305590 removed some, but apparently not all.
24-07-2024
The style guide should be updated to permit using noexcept before making changes to use it. That style guide update is not as simple as just allowing noexcept - it needs to list the places where it may be used.
29-09-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/15910 Date: 2023-09-26 02:50:57 +0000
26-09-2023