[PATCH] D53866: [Preamble] Stop circular inclusion of main file when building preamble

2020-11-05 Thread Jan Wassenberg via Phabricator via cfe-commits
jan-wassenberg added a comment.

@nik here's an unusual but real-world example that triggers this.
https://github.com/google/highway compiles the same source multiple times (with 
different macros set) for generating code for multiple SIMD instruction sets.
The main source file sets a macro to its filename and includes a 
"foreach_target.h" which includes the file identified by that macro.

I understand this is complicated for analysis, so foreach_target.h does nothing 
if it detects that an IDE/analyzer are parsing. This relies on predefined 
macros such as
__CDT_PARSER__ __INTELLISENSE__ Q_CREATOR_RUN. Is there such a macro for clangd?


Repository:
  rC Clang

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D53866/new/

https://reviews.llvm.org/D53866

___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits


[PATCH] D152879: [RISCV] Model vxrm control for vsmul, vssra, vssrl, vnclip, and vnclipu

2023-06-22 Thread Jan Wassenberg via Phabricator via cfe-commits
jan-wassenberg added a comment.

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.


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


[PATCH] D152879: [RISCV] Model vxrm control for vsmul, vssra, vssrl, vnclip, and vnclipu

2023-06-22 Thread Jan Wassenberg via Phabricator via cfe-commits
jan-wassenberg added a comment.

Thanks for your quick reply. Yes, we are tracking trunk with a short lag, and 
unfortunately this is mostly beyond our control.
Now that I have updated the Highway code and toolchain reference in user code, 
we are fine for the moment.
Please do update the intrinsics version number when there is a breaking change, 
though :)


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