Description
This may permit the compiler to generate better code in some cases. This matters even for production, since some of the operations (such as `guarantee` and `ShouldNotReachHere`) are present in product builds, not just debug builds.
This also addresses the problems encountered in
Of course, marking these functions noreturn will require actually making them not return. That's going to require some significant changes.
Attachments
Issue Links
- is blocked by
-
JDK-8302124 HotSpot Style Guide should permit noreturn attribute
-
- Resolved
-
-
JDK-8302262 Remove -XX:SuppressErrorAt develop option
-
- Resolved
-
-
JDK-8302798 Refactor -XX:+UseOSErrorReporting for noreturn crash reporting
-
- Resolved
-
-
JDK-8302799 Refactor Debugging variable usage for noreturn crash reporting
-
- Resolved
-
- relates to
-
JDK-8303805 [REDO] JDK-8302189 and JDK-8302799
-
- Resolved
-
-
JDK-8303797 Replace vmassert constexpr detection with std::is_constant_evaluated
-
- Closed
-
-
JDK-8294031 GCC 12 fails to compile AArch64 due to -Wstringop-overflow
-
- Resolved
-