- Feb 16, 2022
-
-
Krzysztof Drewniak authored
Differential Revision: https://reviews.llvm.org/D119852
-
Marek Kurdej authored
Fixes https://github.com/llvm/llvm-project/issues/53843. Reviewed By: HazardyKnusperkeks, owenpan Differential Revision: https://reviews.llvm.org/D119814
-
Tue Ly authored
Simplify the logic when the exponent difference is at least MantissaLength + 2, while still maintaining correct rounding for all rounding modes. Reviewed By: sivachandra Differential Revision: https://reviews.llvm.org/D119843
-
Mark de Wever authored
This avoids using an libc++ internal macro in our tests. Reviewed By: #libc, philnik, ldionne Differential Revision: https://reviews.llvm.org/D119742
-
Craig Topper authored
This is a more generic version of D119110 that uses MaskedValueIsZero to do the matching and SimplifyDemandedBits to remove any unneeded AND instructions. Tests were taken from D119110. Reviewed By: Chenbing.Zheng Differential Revision: https://reviews.llvm.org/D119622
-
Craig Topper authored
Parsing errors aren't handled earlier in all cases. A simple example is llc -mtriple=riscv64 -mattr=+zve32f. If F or Finx is not also specified, this will hit a parse error. Use a fatal_error so that the error is conveyed to the user.
-
Eric Li authored
Previously, Transformer would invoke the consumer once per file modified per match, in addition to any errors encountered. The consumer is not aware of which AtomicChanges come from any particular match. It is unclear which sets of edits may be related or whether an error invalidates any previously emitted changes. Modify the signature of the consumer to accept a set of changes. This keeps related changes (i.e. all edits from a single match) together, and clarifies that errors don't produce partial changes. Reviewed By: ymandel Differential Revision: https://reviews.llvm.org/D119745
-
Louis Dionne authored
This should work now that we are using a matching libunwind.dylib when we run the tests in back-deployment scenarios. The only restriction we have now is to run on macOS x86_64, since that's what the old dylibs were compiled for. This should allow us to move to newer AppleClangs in the CI. As a fly-by, fix missing availability annotations on optional's monadic operations. Differential Revision: https://reviews.llvm.org/D119840
-
Arthur O'Dwyer authored
Incidentally, this removes some unqualified ADL calls to `begin` and `end`. Differential Revision: https://reviews.llvm.org/D119677
-
Krzysztof Drewniak authored
Reviewed By: mehdi_amini Differential Revision: https://reviews.llvm.org/D119774
-
Alexey Bataev authored
NFC.
-
Arthur O'Dwyer authored
As suggested in D117966. These conditional noexcepts are *permitted* by the Standard (as long as there were no mistakes in them, I guess); but not *mandated*. The Standard doesn't put any noexcept-specifications on these member functions. The same logic would apply to `transform_view::iterator::operator*` and `transform_view::iterator::operator[]`, but the Standard mandates conditional noexcept on `iter_move(transform_view::iterator)`, and I think it doesn't make much sense to say "moving from this iterator is conditionally noexcept but not-moving from it is noexcept(false)," so I'm leaving transform_view alone for now. Differential Revision: https://reviews.llvm.org/D119374
-
- Feb 15, 2022
-
-
Andrew Wei authored
Based on original tests from D119839. See https://github.com/llvm/llvm-project/issues/53853
-
Sanjay Patel authored
A more general enhancement needs to add tests and make sure that intrinsics that return structs are correct. There are also target-specific intrinsics, and I'm not sure what behavior is expected for those.
-
Sanjay Patel authored
A more general enhancement needs to add tests and make sure that intrinsics that return structs are correct. There are also target-specific intrinsics, and I'm not sure what behavior is expected for those.
-
Sanjay Patel authored
-
Arthur O'Dwyer authored
In src/, most files can use `constinit` directly because they're always compiled with C++20. But some files, like "libcxxabi/src/fallback_malloc.cpp", can't, because they're `#include`d directly from test cases in libcxxabi/test/ and therefore must (currently) compile as C++03. We might consider refactoring those offending tests, or at least marking them `UNSUPPORTED: c++03`. Differential Revision: https://reviews.llvm.org/D119264
-
Arthur O'Dwyer authored
[libc++] [test] Split "UNSUPPORTED: libcpp-no-concepts, libcpp-has-no-incomplete-ranges" onto two lines. NFC.
-
Arthur O'Dwyer authored
The logic here is that we are disabling *only* things in `std::ranges::`. Everything in `std::` is permitted, including `default_sentinel`, `contiguous_iterator`, `common_iterator`, `projected`, `swappable`, and so on. Then, we include anything from `std::ranges::` that is required in order to make those things work: `ranges::swap`, `ranges::swap_ranges`, `input_range`, `ranges::begin`, `ranges::iter_move`, and so on. But then that's all. Everything else (including notably all of the "views" and the `std::views` namespace itself) is still locked up behind `_LIBCPP_HAS_NO_INCOMPLETE_RANGES`. Differential Revision: https://reviews.llvm.org/D118736
-
Shraiysh Vaishay authored
`kEmitAccessorPrefix_Raw ` is being removed, and so updating the accessors to `kEmitAccessorPrefix_Prefixed`. Reviewed By: clementval Differential Revision: https://reviews.llvm.org/D119812
-
Matt Devereau authored
Differential Revision: https://reviews.llvm.org/D119453 Co-authored-by:
George Steed <george.steed@arm.com>
-
Valentin Clement authored
This patch adds lowering of ranked array as function return. This patch is part of the upstreaming effort from fir-dev branch. Reviewed By: PeteSteinfeld Differential Revision: https://reviews.llvm.org/D119835 Co-authored-by:
Jean Perier <jperier@nvidia.com>
-
Max Kazantsev authored
Does not affect default behavior (transform is on).
-
Amy Kwan authored
This patch updates the handling of vectors in getPreferredVectorAction(): For single-element and scalable vectors, fall back to default vector legalization handling. For vNi1 vectors, add handling to either split or promote them in order to prevent the production of wide v256i1/v512i1 types. The following assertion is fixed by this patch, as we ended up producing the wide vector types (that are used for MMA) in the backend prior to this fix. ``` Assertion failed: VT.getSizeInBits() == Operand.getValueSizeInBits() && "Cannot BITCAST between types of different sizes!" ``` Differential Revision: https://reviews.llvm.org/D119521
-
zhijian authored
Summary: Added a new option "-X" to specify, which type of object file should be examine. For example: 1. "llvm-nm -X64 archive.a" only deal with the 64bit object files in the archive.a ,ignore the all 32bit object files in the archive.a 2. "llvm-nm -X32 xcoffobj32.o xcoffobj64.o " only deal with the 32bit object file "xcoffobj32.o" , 64bit object file "xcoffobj64.o" will be ignored Reviewers: James Henderson,Fangrui Song Differential Revision: https://reviews.llvm.org/D118193
-
Aaron Ballman authored
A significant number of our tests in C accidentally use functions without prototypes. This patch converts the function signatures to have a prototype for the situations where the test is not specific to K&R C declarations. e.g., void func(); becomes void func(void); This is the tenth batch of tests being updated (there are a significant number of other tests left to be updated).
-
Louis Dionne authored
The test would trigger -Wtautological-compare. I think that the little we gain from comparing addresses isn't worth the added complexity to work around the warning.
-
Simon Pilgrim authored
Extend the existing split where we already do this for v32i16/v64i8 We can end up trying to use PCMPEQ/GT if the result needs to be sign-extended (typically due to the DAGCombiner::foldSextSetcc fold). Fixes #53842
-
Adrian Kuegel authored
Differential Revision: https://reviews.llvm.org/D119832
-
Benjamin Kramer authored
-
Alexander Potapenko authored
This reverts commit dd145f95. https://reviews.llvm.org/D119726, like https://reviews.llvm.org/D114421, still causes TSan to fail, see https://lab.llvm.org/buildbot/#/builders/70/builds/18020 Differential Revision: https://reviews.llvm.org/D119838
-
Ivan Butygin authored
Differential Revision: https://reviews.llvm.org/D119632
-
Xing Xue authored
Summary: The pragma priority guarded for AIX in locale.cpp is no longer useful and is ignored by the current AIX build compilers. This patch removes it from the source. Reviewed by: ldionne, hubert.reinterpretcast, libc++ Differential Revision: https://reviews.llvm.org/D119765
-
Sanjay Patel authored
Integer min/max operations are associative: max (max X, C0), C1 --> max X, (max C0, C1) --> max X, NewC https://alive2.llvm.org/ce/z/wW5HVM This would avoid a regression when we canonicalize to min/max intrinsics (see D98152 ). Differential Revision: https://reviews.llvm.org/D119754
-
Max Kazantsev authored
-
Simon Pilgrim authored
As noted on PR53610, we can fold a 'bit splat' negation of a shifted bitmask pattern into a pair of shifts. https://alive2.llvm.org/ce/z/eGrsoN Differential Revision: https://reviews.llvm.org/D119715
-
Anton Afanasyev authored
Particularly this breaks vectorization of insertelements where some of intermediate (i.e. not last) insertelements are used externally. Fixes PR52275 Fixes #51617 Differential Revision: https://reviews.llvm.org/D119679
-
Anton Afanasyev authored
-
Alexander Potapenko authored
For ASan this will effectively serve as a synonym for __attribute__((no_sanitize("address"))) This is a reland of https://reviews.llvm.org/D114421 Reviewed By: melver, eugenis Differential Revision: https://reviews.llvm.org/D119726 -
Adrian Kuegel authored
-