Currently, compiler-related tests frequently use the architecture descriptor string (e.g., aarch64, x86) to determine if a certain compiler feature is available on the platform where the JVM is executing. If the tested features is a compiler intrinsic, using architecture descriptor strings is an inaccurate way of determining if the intrinsic is available. The reason is that the availability of compiler intrinsics is guided by many factors (e.g., the value of command line flags and instructions available on the platform) and as a result a test might expect an intrinsic to be available when it is in fact not available.

This enhancement proposes adding a new WhiteBox method, is_compiled_intrinsic_availabe(Executable method, int compileLevel) that returns true if an intrinsic for method 'method' is available at compile level 'compileLevel' (the final API might differ from the proposed API).

To test the new new API, existing tests in hotspot/test/compiler/intrinsics/mathexact/sanity will be updated to use the newly added WhiteBox method.