- Feb 18, 2022
-
-
Sebastian Neubauer authored
Same as on vgpr copies, we cannot kill the source register if it overlaps with the destination register. Otherwise, the kill of the source register will also count as a kill for the destination register. Differential Revision: https://reviews.llvm.org/D120042
-
Joseph Huber authored
One of the optimizations performed in OpenMPOpt pushes globalized variables to static shared memory. This is preferable to keeping the runtime call in all cases, however if too many variables are pushed to hared memory the kernel will crash. Since this is an optimization and not something the user specified explicitly, there should be an option to limit this optimization in those cases. This path introduces the `-openmp-opt-shared-limit=` option to limit the amount of bytes that will be placed in shared memory from HeapToShared. Reviewed By: jdoerfert Differential Revision: https://reviews.llvm.org/D120079
-
Joseph Huber authored
The runtime uses thread state values to indicate when we use an ICV or are in nested parallelism. This is done for OpenMP correctness, but it not needed in the majority of cases. The new flag added is `-fopenmp-assume-no-thread-state`. Reviewed By: jdoerfert Differential Revision: https://reviews.llvm.org/D120106
-
Luo, Yuanke authored
-
Alexey Bataev authored
If the alternate cmp instruction is a swapped predicate of the main cmp instruction, need to generate alternate instruction, not the one with the swapped predicate. Also, the lane with the alternate opcode should be selected only, if the corresponding operands are not compatible. Correctness confirmed: https://alive2.llvm.org/ce/z/94BG66 Differential Revision: https://reviews.llvm.org/D119855
-
Simon Moll authored
The broadcast patterns for all-true|false masks are available now. Enable the true|fast fcmp predicate tests that use them. Reviewed By: kaz7 Differential Revision: https://reviews.llvm.org/D119936
-
Simon Moll authored
vmp0 is the all-ones v512i1 register and does not break down into subregisters. Reviewed By: kaz7 Differential Revision: https://reviews.llvm.org/D120054
-
Benjamin Kramer authored
This subsumes the builder and verifier.
-
Florian Hahn authored
-
Nico Weber authored
-
Pavel Labath authored
This patch adds introduces a new kind of an lldbinit file. Unlike the lldbinit in the home directory (useful for customizing lldb to the needs of a particular user), or the cwd lldbinit file (useful for project-specific settings), this file can be used to customize an entire lldb installation to a particular environment. The feature is enabled at build time, by setting the LLDB_GLOBAL_INIT_DIRECTORY variable to a path to a directory which should contain an "lldbinit" file. Lldb will then load the file at startup, if it exists, and if automatic init loading has not been disabled. Relative paths will be resolved (at runtime) relative to the location of the lldb library (liblldb or LLDB.framework). The system-wide lldbinit file will be loaded first, before any $HOME/.lldbinit and $CWD/.lldbinit files are processed, so that those can override any system-wide settings. More information can be found on the RFC thread at <https://discourse.llvm.org/t/rfc-system-...
-
Simon Pilgrim authored
-
Tres Popp authored
insert is soft deprecated, so remove all references so it's less likely to be used and can be easily removed in the future. Differential Revision: https://reviews.llvm.org/D120021
-
Kadir Cetinkaya authored
Allocate on ASTContext, rather than just on heap, so that template parameter lists are freed up. Differential Revision: https://reviews.llvm.org/D120081
-
Simon Pilgrim authored
The DC pointer is always dereferenced after the loop
-
Pavel Labath authored
It breaks TestVSCode_attach.py. This reverts commit 9febd1e5 and 38054556.
-
Florian Hahn authored
This reverts commit 1689b109. This patch was only added to fix a failure with 32b73bc6, which has been reverted again.
-
Florian Hahn authored
This reverts commit 32b73bc6. This breaks builds on macOS in some configurations, because __FLT_EVAL_METHOD__ is set to an unexpected value. E.g. https://green.lab.llvm.org/green/job/clang-stage1-RA/28282/consoleFull#129538464349ba4694-19c4-4d7e-bec5-911270d8a58c More details available in the review thread https://reviews.llvm.org/D109239
-
Benjamin Kramer authored
This is a bit awkward since ExtractOp allows both `f32` and `vector<1xf32>` results for a scalar extraction. Allow both, but make inference return the scalar to make this as NFC as possible.
-
Matthias Springer authored
Differential Revision: https://reviews.llvm.org/D119824
-
Simon Pilgrim authored
[Hexagon] aligned load/store patterns - use cast<> instead of dyn_cast<> to avoid dereference of nullptr The pointer is always referenced inside isAlignedMemNode, so assert the cast is correct instead of returning nullptr
-
Simon Pilgrim authored
The MMI pointer has already been dereferenced several times.
-
Jay Foad authored
Differential Revision: https://reviews.llvm.org/D120023
-
Matthias Springer authored
Differential Revision: https://reviews.llvm.org/D119935
-
Alexey Lapshin authored
This patch adds rules to cmake to put files under specific folders. It allows to have files for different formats(which are located in different subdirectories) be displayed in different subfolders of VS IDE solution. Depends on D114429 Differential Revision: https://reviews.llvm.org/D114664
-
Jay Foad authored
Differential Revision: https://reviews.llvm.org/D120025
-
Jay Foad authored
Differential Revision: https://reviews.llvm.org/D120024
-
Douglas Yung authored
-
Jay Foad authored
Differential Revision: https://reviews.llvm.org/D119954
-
Stephan Herhut authored
This change changes the handling of trailing dimensions with unknown extent. Users of the changessociationIndicesForReshape helper should see benefits when transforming reshape like operations into expand/collapse pairs if the higher-rank type has trailing unknown dimensions. The motivating example is a reshape from tensor<16x1x?xi32> to tensor<16xi32> that can be modeled as collapsing the three dimensions. Differential Revision: https://reviews.llvm.org/D119730
-
hyeongyukim authored
-
Alexander Potapenko authored
For ASan this will effectively serve as a synonym for __attribute__((no_sanitize("address"))). Adding the disable_sanitizer_instrumentation to functions will drop the sanitize_XXX attributes on the IR level. This is the third reland of https://reviews.llvm.org/D114421. Now that TSan test is fixed (https://reviews.llvm.org/D120050) there should be no deadlocks. Differential Revision: https://reviews.llvm.org/D120055 -
hyeongyukim authored
-
Tres Popp authored
Previously, NaNs would be dropped in favor of bounded values which was strictly incorrect. Now the min/max operation propagate this information. Not all uses of min/max need this, but the given change will help protect future additions, and this prevents the need for an additional cmpf and select operation to handle NaNs. Differential Revision: https://reviews.llvm.org/D120020
-
hyeongyukim authored
This flag was previously renamed `enable_noundef_analysis` to `disable-noundef-analysis,` which is not a conventional name. (Driver and CC1's boolean options are using [no-] prefix) As discussed at https://reviews.llvm.org/D105169, this patch reverts its name to `[no-]enable_noundef_analysis` and enables noundef-analysis as default. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D119998
-
https://reviews.llvm.org/D119797Greg Clayton authored
This value error is no longer needed with the new version of the patch
-
Valentin Clement authored
Handle negation on scalar expression. ``` res = -a ``` This patch is part of the upstreaming effort from fir-dev branch. Reviewed By: PeteSteinfeld Differential Revision: https://reviews.llvm.org/D120071 Co-authored-by:
Jean Perier <jperier@nvidia.com> Co-authored-by:
Eric Schweitz <eschweitz@nvidia.com>
-
LLVM GN Syncbot authored
-
Snehasish Kumar authored
This patch adds support for optional memory profile information to be included with and indexed profile. The indexed profile header adds a new field which points to the offset of the memory profile section (if present) in the indexed profile. For users who do not utilize this feature the only overhead is a 64-bit offset in the header. The memory profile section contains (1) profile metadata describing the information recorded for each entry (2) an on-disk hashtable containing the profile records indexed via llvm::md5(function_name). We chose to introduce a separate hash table instead of the existing one since the indexing for the instrumented fdo hash table is based on a CFG hash which itself is perturbed by memprof instrumentation. This commit also includes the changes reviewed separately in D120093. Differential Revision: https://reviews.llvm.org/D120103
-