eopXD added a comment. In D152879#4440356 <https://reviews.llvm.org/D152879#4440356>, @jan-wassenberg wrote:
> Is there a way to detect whether the compiler already includes this change, > preferably via preprocessor? > I tried `#ifdef __RISCV_VXRM_RDN` and `#if __has_builtin(__RISCV_VXRM_RDN)`. > > This is a breaking change for us. Updating code to the new required signature > fails to compile on the older toolchain (which is still in use). Leaving the > code in the old style (no extra VXRM argument) is also not an option because > other users have already updated their LLVM. Hi Jan, Thanks for checking. I was planning to bump the version number of the RVV intrinsics [0] in the next LLVM release for users to identify what version of intrinsics they are using. My fault for not being aware that projects may be using the trunk upstream compiler. Temporarily, I can add an indicator for users to identify this breaking change, however the new LLVM branch out is coming on July 4th, so I personally think we should just bump the version number for the next LLVM release. If this is a really urgent issue, lets discuss more. [0] https://github.com/llvm/llvm-project/blob/main/clang/lib/Basic/Targets/RISCV.cpp#L200 Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D152879/new/ https://reviews.llvm.org/D152879 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
