This project is mirrored from https://github.com/llvm/llvm-project.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
- Apr 07, 2022
-
-
Simon Pilgrim authored
-
Nathan Sidwell authored
Internal symbol mangling is implementation-defined. We do not mangle any module attachment, and this adds a test to verify that. Reviewed By: dblaikie Differential Revision: https://reviews.llvm.org/D123220
-
Antonio Frighetto authored
clang may throw the following warning: include/clang/AST/DeclarationName.h:210:52: error: arithmetic between different enumeration types ('clang::DeclarationName::StoredNameKind' and 'clang::detail::DeclarationNameExtra::ExtraKind') is deprecated when flags -Werror,-Wdeprecated-enum-enum-conversion are on. This adds the `addEnumValues()` helper function to STLExtras.h to hide the details of adding enumeration values together from two different enumerations.
-
Nico Weber authored
-
Nico Weber authored
-
Nico Weber authored
This matches ld64, and makes dsymutil work better with lld's output. Fixes PR54783, see there for details. Reduces time needed to run dsymutil on Chromium Framework from 8m30s (which is already down from 26 min with D123218) to 6m30s and removes many lines of "could not find object file symbol for symbol" from dsymutil output (previously: several MB of those messages, now dsymutil is completely silent). Differential Revision: https://reviews.llvm.org/D123252
-
Nikolas Klauser authored
There are `constexpr` versions for the different `__invoke` functions, which seem to be identical other than begin `constexpr` since C++11 instead of being `constexpr` since C++20. Reviewed By: ldionne, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D123003
-
Nikita Popov authored
This was accidentally caught in an automated replacement. This test is testing the -opaque-pointers flag itself, so we shouldn't add -no-opaque-pointers here (though it doesn't hurt either). Also drop the line testing the default, as the default is now determined by a cmake option.
-
Kavitha Natarajan authored
clang to emit DWARF information for global alias variable as DW_TAG_imported_declaration. This change also handles nested (recursive) imported declarations. Reviewed by: dblaikie, aprantl Differential Revision: https://reviews.llvm.org/D120989
-
Weining Lu authored
This change removes a lot of redundant strconcat usings.
-
Simon Pilgrim authored
[bugpoint] ReduceCrashingFunctions::TestFuncs - fix dereference of null point static analyzer warning Alias.getAliaseeObject() shouldn't be null, do use dyn_cast instead of dyn_cast_or_null Also, remove redundant `else if (!F)` test - that is always true at the point in the if-else chain
-
Priyansh Singh authored
-
chenglin.bi authored
-
Luís Marques authored
The existing code wasn't getting the subtarget info from the fragment, so the current status of RVC would be ignored. This would cause a crash for the new test case when the target then reported it couldn't write the requested number of code alignment bytes. Differential Revision: https://reviews.llvm.org/D122236
-
Chih-Ping Chen authored
array index type.
-
Kirill Bobyrev authored
-
Nikita Popov authored
This adds the flag to more tests that were not caught by the mass-migration in 532dc62b.
-
Zi Xuan Wu authored
In soft ABI, floating num is passing in GPRs. So we need support bitcovert from double to Hi and Lo GPRs and vice versa
-
Simon Pilgrim authored
-
Simon Pilgrim authored
-
Benjamin Kramer authored
-
Nikita Popov authored
This adds -no-opaque-pointers to clang tests whose output will change when opaque pointers are enabled by default. This is intended to be part of the migration approach described in https://discourse.llvm.org/t/enabling-opaque-pointers-by-default/61322/9. The patch has been produced by replacing %clang_cc1 with %clang_cc1 -no-opaque-pointers for tests that fail with opaque pointers enabled. Worth noting that this doesn't cover all tests, there's a remaining ~40 tests not using %clang_cc1 that will need a followup change. Differential Revision: https://reviews.llvm.org/D123115
-
Nikolas Klauser authored
Reviewed By: ldionne, var-const, #libc Spies: libcxx-commits Differential Revision: https://reviews.llvm.org/D122011
-
Mehdi Chinoune authored
It was broken since https://reviews.llvm.org/D110172 Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D122523
-
Lorenzo Chelini authored
Remove duplicate statements.
-
Martin Storsjö authored
This warning gives false positives about lldb's correct use of strncpy to fill fixed length fields that don't need null termination, in lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp, like this: In file included from /usr/include/string.h:495, from /usr/include/c++/9/cstring:42, from ../include/llvm/ADT/StringRef.h:19, from ../tools/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp:10: In function ‘char* strncpy(char*, const char*, size_t)’, inlined from ‘lldb::offset_t CreateAllImageInfosPayload(const ProcessSP&, lldb::offset_t, lldb_private::StreamString&, lldb::SaveCoreStyle)’ at ../tools/lldb/source/Plugins/ObjectFile/Mach-O/ObjectFileMachO.cpp:6341:16: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:34: warning: ‘char* __builtin_strncpy(char*, const char*, long unsigned int)’ specified bound 16 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~ The warning could be squelched locally with #pragma GCC diagnostic ignored "-Wstringop-truncation" too, but Clang also interprets those GCC pragmas, and produces a -Wunknown-warning-option warning instead. That could be remedied by wrapping the pragma in an "#ifndef __clang__" - but that makes things even more messy. Instead, just silence this warning entirely. Differential Revision: https://reviews.llvm.org/D123254
-
Balázs Kéri authored
The error can be returned from the function, the problem written in comment before does not exist. The same is done already in ASTImporter at various import failures. After a declaration is created in an `ASTNodeImporter` import function with `GetImportedOrCreateDecl`, that function registers it with `MapImported`. At many places import errors can happen after this and the error is returned. The same can be done in the place where the in-class initializer is imported. Reviewed By: martong Differential Revision: https://reviews.llvm.org/D122528
-
Benjamin Kramer authored
-
Weining Lu authored
-
Fraser Cormack authored
This patch has no effect on the generated code, whilst mitigating the increase in ISel table size caused by the recent addition of masked patterns. I aim to do the same for floating-point patterns once D123051 lands, giving us a reason to use masked floating-point patterns. Reviewed By: arcbbb Differential Revision: https://reviews.llvm.org/D123217
-
Benjamin Kramer authored
-
Benjamin Kramer authored
Utils can't depend on Scalar transforms.
-
Florian Hahn authored
This brings the VPlan block naming in line with the naming of the generated basic blocks.
-
Fraser Cormack authored
This patch adds the necessary infrastructure to lower vp.fcmp via ISD::VP_SETCC to RVV instructions. Most notably this patch adds cond-code legalization for VP_SETCC, reusing the existing TargetLowering::LegalizeSetCCCondCode by passing in additional SDValue parameters for the Mask and EVL. This method then uses VP operations to legalize the condcode. There is still a general lack of canonicalization on VP_SETCC as opposed to SETCC which results in worse code than is theoretically possible. Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D123051
-
Nikita Popov authored
This removes options for performing LTO with the legacy pass manager in LLD. Options that explicitly enable the new pass manager are retained as no-ops. Differential Revision: https://reviews.llvm.org/D123219
-
Nikita Popov authored
This option controls whether -opaque-pointers or -no-opaque-pointers is the default. Once opaque pointers are enabled by default, this will provide a simple way to temporarily opt-out of the change. Differential Revision: https://reviews.llvm.org/D123122
-
Valentin Clement authored
This patch enhances the CSE pass to deal with simple cases of duplicated operations with MemoryEffects. It allows the CSE pass to remove safely duplicate operations with the MemoryEffects::Read that have no other side-effecting operations in between. Other MemoryEffects::Read operation are allowed. The use case is pretty simple so far so we can build on top of it to add more features. This patch is also meant to avoid a dedicated CSE pass in FIR and was brought together afetr discussion on https://reviews.llvm.org/D112711. It does not currently cover the full range of use cases described in https://reviews.llvm.org/D112711 but the idea is to gradually enhance the MLIR CSE pass to handle common use cases that can be used by other dialects. This patch takes advantage of the new CSE capabilities in Fir. Reviewed By: mehdi_amini, rriddle, schweitz Differential Revision: https://reviews.llvm.org/D122801
-
Wei Xiao authored
smin(x, 0): (select (x < 0), x, 0) -> ((x >> (size_in_bits(x)-1))) & x smax(x, 0): (select (x > 0), x, 0) -> (~(x >> (size_in_bits(x)-1))) & x The comparison is testing for a positive value, we have to invert the sign bit mask, so only do that transform if the target has a bitwise 'and not' instruction (the invert is free). The transform is performed only when CMP has a single user to avoid increasing total instruction number. https://alive2.llvm.org/ce/z/euUnNm https://alive2.llvm.org/ce/z/37339J Differential Revision: https://reviews.llvm.org/D123109
-
Nikita Popov authored
LoopSink with the legacy pass manager still uses AST, because we can't compute MemorySSA conditionally. I think now that the legacy pass manager will be removed soon(TM) we don't need to care about compile-time impact here anymore. Additionally, since MemorySSA is no longer eagerly optimized, the impact is actually not that high anymore (~0.2% geomean regression on CTMark). This just makes legacy PM and new PM behavior line up -- as a followup I'll drop these options entirely and make MemorySSA use mandatory. Differential Revision: https://reviews.llvm.org/D123216
-
Balázs Kéri authored
Another change of the code design. Code simplified again, now there is a single place to check a handler function and less functions for bug report emitting. More details are added to the bug report messages. Reviewed By: whisperity Differential Revision: https://reviews.llvm.org/D118370
-