diff options
| author | Dominik Adamski <dominik.adamski@amd.com> | 2023-01-17 03:51:48 -0600 |
|---|---|---|
| committer | Dominik Adamski <dominik.adamski@amd.com> | 2023-01-26 15:10:19 -0600 |
| commit | ca446037af019d1aa01b1352a30a18df33038359 (patch) | |
| tree | 9824c1d8627b8868637930c90bff1d9853446806 /llvm/lib/CodeGen/StackProtector.cpp | |
| parent | f9839876574fe97fdcdf104fbb1c9ba7fd4f9433 (diff) | |
| download | llvm-ca446037af019d1aa01b1352a30a18df33038359.zip llvm-ca446037af019d1aa01b1352a30a18df33038359.tar.gz llvm-ca446037af019d1aa01b1352a30a18df33038359.tar.bz2 | |
[OpenMP][OMPIRBuilder]Move SIMD alignment calculation to LLVM Frontend
Currently default simd alignment is defined by Clang specific TargetInfo class.
This class cannot be reused for LLVM Flang. That's why default simd alignment
calculation has been moved to OMPIRBuilder which is common for Flang and Clang.
Previous attempt: https://reviews.llvm.org/D138496 was wrong because
the default alignment depended on the number of built LLVM targets.
If we wanted to calculate the default alignment for PPC and we hadn't specified
PPC LLVM target to build, then we would get 0 as the alignment because
OMPIRBuilder couldn't create PPCTargetMachine object and it returned 0 as
the default value.
If PPC LLVM target had been built earlier, then OMPIRBuilder could have created
PPCTargetMachine object and it would have returned 128.
Differential Revision: https://reviews.llvm.org/D141910
Reviewed By: jdoerfert
Diffstat (limited to 'llvm/lib/CodeGen/StackProtector.cpp')
0 files changed, 0 insertions, 0 deletions