On Thu, 11 Sep 2025 09:43:36 GMT, SendaoYan <[email protected]> wrote:
>> Hi all, >> >> Build jdk on linux-aarch64 with older assembler version(as 2.30) will report >> compilation failre, shows as >> [JDK-8366777](https://bugs.openjdk.org/browse/JDK-8366777). >> >> This PR add the expression `svfloat64_t a() {}` to makefile which will >> trigger the compilation during configure stage. After this PR, at configure >> stage will check the gcc and assember support `-march=armv8-a+sve` or not >> more comprehensive. >> >> Testing: >> - [x] On linux-aarch64 gcc12.3.1 as2.37, configure set SVE_CFLAGS as >> '-march=armv8-a+sve' >> - [x] On linux-aarch64 gcc10.3.0 as2.30, configure set SVE_CFLAGS as empty >> >> >> The compilation fails demo as below: >> >> >> # cat sve.c >> #include <arm_sve.h> >> svfloat64_t a() {} >> # gcc -march=armv8-a+sve sve.c >> /tmp/ccVOzMzb.s: Assembler messages: >> /tmp/ccVOzMzb.s:6: Error: unknown pseudo-op: `.variant_pcs' > > SendaoYan has updated the pull request incrementally with one additional > commit since the last revision: > > Use lambda with CHECK_AVAIABLE Job https://github.com/sendaoYan/jdk-ysd/actions/runs/17640542609/job/50126351415 report build fails, since the compiler(clang-15) on macos-aarch64 generate Segmentation fault error with -march=armv8-a+sve option when buiding the libsleef. This because the [patchset](https://github.com/openjdk/jdk/pull/27073/commits/5f16605149369456b3fdd9a0b1fb229d3d6388e2) make aarch64-sve enable by default. The `UTIL_ARG_ENABLE(NAME: aarch64-sve)` has no change to be invoked during configure stage. It's no expected. ------------- PR Comment: https://git.openjdk.org/jdk/pull/27073#issuecomment-3280414263
