[vectorIntrinsics] RFR: 8260668: vectorIntrinsics windows build problem
Magnus Ihse Bursie
ihse at openjdk.java.net
Mon Feb 1 13:19:57 UTC 2021
On Fri, 29 Jan 2021 19:25:31 GMT, Sandhya Viswanathan <sviswanathan at openjdk.org> wrote:
> The panama-vector vectorIntrinsics branch fails to build on windows.
> This is happening because /Ta option is no more supported by the VS2019 C compiler to generate obj from assembly files.
> The alternative is to use the windows assembler instead for this purpose.
> Best Regards,
Changes requested by ihse (no project role).
make/autoconf/toolchain.m4 line 699:
> 697: AS="$CC -c"
> 698: else
> 699: if test "x$OPENJDK_TARGET_CPU" = "xx86_64"; then
Is the proper test for x86_64 or for 64-bit CPUs? Or phrased differently, what is the name of the executable on aarch64? The comment below states that the test is for word size, but the test itself is for CPU architecture.
src/hotspot/os_cpu/windows_x86/globals_vectorApiSupport_windows.hpp line 1:
> 1: ; Copyright (c) 1997, 2021, Oracle and/or its affiliates. All rights reserved.
Maybe you have already established this as a new convention, but I think it is highly confusing to have a file named `.hpp` which is not a C++ header file! I expect IDEs etc will get confused too, and complain about syntax errors. Recommend renaming it to something different. If no conventional suffix exists for assembly language includes, perhaps just name it `.s.inc`?
make/common/NativeCompilation.gmk line 442:
> 440: $$($1_COMPILER) $$($1_FLAGS) \
> 441: $(CC_OUT_OPTION)$$($1_OBJ) /nologo /c /Ta $$($1_SRC_FILE) 2>&1 \
> 442: | $(TR) -d '\r' | $(GREP) -v -e "Assembling:" || test "$$$$?" = "1" ;))
Please use the `-nologo -c -Ta` format for the options.
More information about the panama-dev