RFR: JDK-8321017: Record in JFR that IEEE rounding mode was corrupted by loading a library [v2]

[Matthias Baesken]

On Mon, 4 Dec 2023 09:06:04 GMT, Thomas Stuefe <stuefe at openjdk.org> wrote:

> I also think it seems odd to include it in JFR.
> 

If you look at the JFR goal  "Provide a low-overhead data collection framework for troubleshooting Java applications and the HotSpot JVM."   (https://openjdk.org/jeps/328)  I think this fits quite well into the "troubleshooting" part.
Not saying that your idea

> As an alternative, I propose to put a test for that condition into the JNI checker (`-Xcheck:jni`). The point of that option is to check third-party native code for problems, so its a perfect fit.

is bad; what do others think ?
My concern here is that the JNI checker  (JNI checker (`-Xcheck:jni`)) is probably even less used than JFR. But I might be wrong.
The cases where we directly dlopen/dlsym/fcn-call in the JDK codebase are probably not covered by the JNI checker, right ?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/16903#issuecomment-1838452407