| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[Clang][AMDGPU] Use 32-bit index for SWMMAC builtins (#129101) Currently, the index of SWMMAC builtins is of type short, likely based on the assumption that K can only be up to 32, meaning there are only 16 non-zero elements. However, this is not future-proof. This patch updates all of them to int. The intrinsics themselves don't need to be updated since they accept any integer type, and in the backend, they are already extended to 32-bit. Additionally, the tests already use various kinds of integers. Partially fixes SWDEV-518183. | 1 年前 | |
[llvm][DebugInfo] Unwrap template parameters that are typedefs when reconstructing DIE names (#168734) Depends on: * https://github.com/llvm/llvm-project/pull/168725 When compiling with -glldb, we repoint the DW_AT_type of a DIE to be a typedef that refers to the preferred_name. I.e.,: template <typename T> structure t7; using t7i = t7<int>; template <typename T> struct __attribute__((__preferred_name__(t7i))) t7 {}; template <typename... Ts> void f1() int main() { f1<t7i>(); } would produce following (minified) DWARF: DW_TAG_subprogram DW_AT_name ("_STN|f1|<t7<int> >") DW_TAG_template_type_parameter DW_AT_type (0x0000299c "t7i") ... DW_TAG_typedef DW_AT_type (0x000029a7 "t7<int>") DW_AT_name ("t7i") Note how the DW_AT_type of the template parameter is a typedef itself (instead of the canonical type). The DWARFTypePrinter would take the DW_AT_name of this typedef when reconstructing the name of f1, so we would end up with a verifier failure: error: Simplified template DW_AT_name could not be reconstituted: original: f1<t7<int> > reconstituted: f1<t7i> Fixing this allows us to un-XFAIL the simplified-template-names.cpp test in cross-project-tests. Unfortunately this is only tested on Darwin, where LLDB tuning is the default. AFAIK, there is no other case where the template parameter type wouldn't be canonical. | 8 个月前 | |
Fixed 2 tests that failed on MacOS (#168482) 1. Fixed 2 DTLTO cache tests that failed on MacOS because input to grep command is different compared to Windows 2. Removed unneeded comments from dtlto-cache.ll | 8 个月前 | |
Wasm fmuladd relaxed (#163177) Reland #161355, after fixing up the cross-projects-tests for the wasm simd intrinsics. Original commit message: Lower v4f32 and v2f64 fmuladd calls to relaxed_madd instructions. If we have FP16, then lower v8f16 fmuladds to FMA. I've introduced an ISD node for fmuladd to maintain the rounding ambiguity through legalization / combine / isel. | 9 个月前 | |
[llvm-objdump][ARM] Find ELF file PLT entries for arm, thumb (#130764) This implements arm, armeb, thumb, thumbeb PLT entries parsing support in ELF for llvm-objdump. Implementation is similar to AArch64MCInstrAnalysis::findPltEntries. PLT entry signatures are based on LLD code for PLT generation (ARM::writePlt). llvm-objdump tests are produced from lld/test/ELF/arm-plt-reloc.s, lld/test/ELF/armv8-thumb-plt-reloc.s. | 1 年前 | |
RuntimeLibcalls: Move VectorLibrary handling into TargetOptions (#167996) This fixes the -fveclib flag getting lost on its way to the backend. Previously this was its own cl::opt with a random boolean. Move the flag handling into CommandFlags with other backend ABI-ish options, and have clang directly set it, rather than forcing it to go through command line parsing. Prior to de68181d7f, codegen used TargetLibraryInfo to find the vector function. Clang has special handling for TargetLibraryInfo, where it would directly construct one with the vector library in the pass pipeline. RuntimeLibcallsInfo currently is not used as an analysis in codegen, and needs to know the vector library when constructed. RuntimeLibraryAnalysis could follow the same trick that TargetLibraryInfo is using in the future, but a lot more boilerplate changes are needed to thread that analysis through codegen. Ideally this would come from an IR module flag, and nothing would be in TargetOptions. For now, it's better for all of these sorts of controls to be consistent. | 8 个月前 | |
RuntimeLibcalls: Move VectorLibrary handling into TargetOptions (#167996) This fixes the -fveclib flag getting lost on its way to the backend. Previously this was its own cl::opt with a random boolean. Move the flag handling into CommandFlags with other backend ABI-ish options, and have clang directly set it, rather than forcing it to go through command line parsing. Prior to de68181d7f, codegen used TargetLibraryInfo to find the vector function. Clang has special handling for TargetLibraryInfo, where it would directly construct one with the vector library in the pass pipeline. RuntimeLibcallsInfo currently is not used as an analysis in codegen, and needs to know the vector library when constructed. RuntimeLibraryAnalysis could follow the same trick that TargetLibraryInfo is using in the future, but a lot more boilerplate changes are needed to thread that analysis through codegen. Ideally this would come from an IR module flag, and nothing would be in TargetOptions. For now, it's better for all of these sorts of controls to be consistent. | 8 个月前 | |
[Dexter] llvm-lit: Always log DAP messages to stderr (#158586) This will help diagnose flaky buildbots. The stderr output is only shown by lit if the test fails. | 10 个月前 | |
Revert "[BOLT] Fix unconditional output of boltedcollection in merge-fdata (#78653)" This reverts commit 82bc33ea3f1a539be50ed46919dc53fc6b685da9. Accidentally pushed unrelated changes. | 2 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 8 个月前 | ||
| 8 个月前 | ||
| 9 个月前 | ||
| 1 年前 | ||
| 8 个月前 | ||
| 8 个月前 | ||
| 10 个月前 | ||
| 2 年前 |