- Oct 08, 2021
-
-
Jake Egan authored
The following tests explicitly check for .loc and .file directives, which is not currently supported. Disable these tests on AIX for now. Reviewed By: shchenz Differential Revision: https://reviews.llvm.org/D111346
-
Stella Laurenzo authored
TensorLiteralParser::getHexAttr does a isIntOrIndexOrFloat check and properly handles index elements, but TensorLiteralParser::getAttr that calls into it has a mismatched check. This just makes the checks match so that index element attrs can parse when of type tensor. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D111374
-
Mark de Wever authored
While looking at the review comments in D103765 there was an oddity in the tests for the following functions: - atomic_fetch_add - atomic_fetch_add_explicit - atomic_fetch_sub - atomic_fetch_sub_explicit Libc++ allows usage of `atomic_fetch_add<int>(atomic<int*>*, atomic<int*>::difference_type);` MSVC and GCC reject this code: https://godbolt.org/z/9d8WzohbE This makes the atomic `fetch(add|sub).*` Standard conforming and removes the non-conforming extensions. Fixes PR47908 Reviewed By: ldionne, #libc Differential Revision: https://reviews.llvm.org/D103983
-
Kazu Hirata authored
The last uses were removed on Oct 7, 2021 in commit 80e39366. This is a relanding of c72722f4.
-
Sanjay Patel authored
-
Sanjay Patel authored
Also regenerate some check lines to more accurately show current transforms via name changes.
-
Shilei Tian authored
It must be a copy mistake. Reviewed By: ye-luo Differential Revision: https://reviews.llvm.org/D111407
-
Louis Dionne authored
It is not used anywhere anymore since we're using the new runtimes build in <monorepo>/runtimes now, so we can remove all traces of this build. Differential Revision: https://reviews.llvm.org/D111351
-
Bradley Smith authored
This reverts commit 3e8d2008. The code removed in this commit is actually required for extracting fixed types from illegal scalable types, hence this commit causes assertion failures in such extracts.
-
Andrzej Warzynski authored
As pointed out by Valentin Clement in PR [1], we should be using `&&` instead of `&`. [1] https://github.com/flang-compiler/f18-llvm-project/pull/1113#discussion_r724321121 Differential Revision: https://reviews.llvm.org/D111395
-
Guillaume Chatelet authored
-
Guillaume Chatelet authored
-
Freddy Ye authored
Reviewed By: DavidSpickett Differential Revision: https://reviews.llvm.org/D110798
-
Qiongsi Wu authored
Objective C is not supported on AIX or ZOS. This patch excludes the newly added `clang/test/Modules/merge-objc-interface.m` (added by https://reviews.llvm.org/D110280) from AIX and ZOS testing. Many existing tests are already disabled by https://reviews.llvm.org/D109060. Reviewed By: jsji Differential Revision: https://reviews.llvm.org/D111406
-
Guillaume Chatelet authored
This reverts commit 1c716030.
-
Guillaume Chatelet authored
-
David Stuttard authored
For PS shaders we can use the input SPI_PS_INPUT_ENA and SPI_PS_INPUT_ADDR registers Calculate the number of VGPR registers used as input VGPRs based on these registers rather than the arguments passed in (this conservatively always allocates the maximum). Differential Revision: https://reviews.llvm.org/D101633 Change-Id: Idf7c060cbbd5f7e3300102c55ecee3c07f209de6
-
Med Ismail Bennani authored
This patch disables TestScriptedProcess.py on Linux and Windows while I investigate the OS specific failure: http://lab.llvm.org:8011/#/builders/68/builds/19793 Signed-off-by:
Med Ismail Bennani <medismail.bennani@gmail.com>
-
Med Ismail Bennani authored
This patch adds support for memory regions in Scripted Processes. This is necessary to read the stack memory region in order to reconstruct each stackframe of the program. In order to do so, this patch makes some changes to the SBAPI, namely: - Add a new constructor for `SBMemoryRegionInfo` that takes arguments such as the memory region name, address range, permissions ... This is used when reading memory at some address to compute the offset in the binary blob provided by the user. - Add a `GetMemoryRegionContainingAddress` method to `SBMemoryRegionInfoList` to simplify the access to a specific memory region. With these changes, lldb is now able to unwind the stack and reconstruct each frame. On top of that, reloading the target module at offset 0 allows lldb to symbolicate the `ScriptedProcess` using debug info, similarly to an ordinary Process. To test this, I wrote a simple program with multiple function calls, ran it in lldb, stop...
-
Med Ismail Bennani authored
This patch introduces the `ScriptedThread` class with its python interface. When used with `ScriptedProcess`, `ScriptedThreaad` can provide various information such as the thread state, stop reason or even its register context. This can be used to reconstruct the program stack frames using lldb's unwinder. rdar://74503836 Differential Revision: https://reviews.llvm.org/D107585 Signed-off-by:
Med Ismail Bennani <medismail.bennani@gmail.com>
-
Kirill Bobyrev authored
-
Michał Górny authored
Open and use the secondary end of a pty for testing Terminal properties in order to fix the tests on Darwin. While at it, streamline getting the fd and Terminal class. Differential Revision: https://reviews.llvm.org/D111402
-
Mirko Brkusanin authored
Differential Revision: https://reviews.llvm.org/D111319
-
Matthias Springer authored
The purpose of this revision is to make "write into non-writable memory" conflict detection easier to understand. The main idea is that there is a conflict in the case of inplace bufferization if: 1. Someone writes to (an alias of) opOperand, opResult or the to-be-bufferized op writes itself. 2. And, opOperand or opResult aliases a non-writable buffer. Differential Revision: https://reviews.llvm.org/D111379
-
Lei Zhang authored
This commit adds a pattern to perform constant folding on linalg generic ops which are essentially transposes. We see real cases where model importers may generate such patterns. Reviewed By: mravishankar Differential Revision: https://reviews.llvm.org/D110597
-
Rajan Walia authored
Add affine demotion pass. Affine dialect's default lowering for loads and stores is different from fir as it uses the `memref` type. The `memref` type is not compatible with the Fortran runtime. Therefore, conversion of memory operations back to `fir.load` and `fir.store` with `!fir.ref<?>` types is required. This patch is part of the upstreaming effort from fir-dev branch. Co-authored-by:
Jean Perier <jperier@nvidia.com> Co-authored-by:
V Donaldson <vdonaldson@nvidia.com> Co-authored-by:
Rajan Walia <walrajan@gmail.com> Co-authored-by:
Sourabh Singh Tomar <SourabhSingh.Tomar@amd.com> Co-authored-by:
Valentin Clement <clementval@gmail.com> Reviewed By: schweitz Differential Revision: https://reviews.llvm.org/D111257
-
Simon Pilgrim authored
[CostModel][TTI] Replace BAD_ICMP_PREDICATE with ICMP_SGT/UGT for generic abs/min/max cost expansion Split off ABS cost handling from MIN/MAX and use explicit predicates for each Our generic expansion of ABS doesn't use NEG+CMP+SELECT any more (its now ASHR+ADD+XOR) so this needs to be updated.
-
LLVM GN Syncbot authored
-
Nico Weber authored
This reverts commit 98d0f8f2. 6fe2beba relanded in 1dba6b37.
-
Corentin Jabot authored
Implement P2360R0 in C++23 mode and as an extension in older languages mode.
-
Max Kazantsev authored
Removed obsolete DT verification that should not be there because the strategy of DT updates has changed. Differential Revision: https://reviews.llvm.org/D110922
-
Jingu Kang authored
This reverts the revert commit fc36fb4d with bug fixes. Differential Revision: https://reviews.llvm.org/D109963
-
Eugene Zhulenev authored
Reviewed By: bkramer Differential Revision: https://reviews.llvm.org/D111364
-
Michał Górny authored
Move the POSIX-specific fd:// and file:// scheme handling into separate methods. Replace the custom GetURLAddress() matching with splitting into scheme and path, and matching scheme via llvm::StringSwitch. Use early returns. Differential Revision: https://reviews.llvm.org/D111321
-
Jean Perier authored
Convert fir operations which satisfy affine constraints to the affine dialect. This patch is part of the upstreaming effort from fir-dev branch. Co-authored-by:
V Donaldson <vdonaldson@nvidia.com> Co-authored-by:
Rajan Walia <walrajan@gmail.com> Co-authored-by:
Sourabh Singh Tomar <SourabhSingh.Tomar@amd.com> Co-authored-by:
Eric Schweitz <eschweitz@nvidia.com> Co-authored-by:
Valentin Clement <clementval@gmail.com> Reviewed By: schweitz, awarzynski Differential Revision: https://reviews.llvm.org/D111155
-
John McCall authored
non-Darwin ObjC runtimes: - Use the same logic the Darwin runtime does for inferring that a receiver is non-null and therefore doesn't require null checks. Previously we weren't skipping these for non-super dispatch. - Emit a null check when there's a consumed parameter so that we can destroy the argument if the call doesn't happen. This mostly involves extracting some common logic from the Darwin-runtime code. - Generate a zero aggregate by zeroing the same memory that was used in the method call instead of zeroing separate memory and then merging them with a phi. This uses less memory and avoids unnecessary copies. - Emit zero initialization, and generate zero values in phis, using the proper zero-value routines instead of assuming that the zero value of the result type has a bitwise-zero representation.
-
Saiyedul Islam authored
An archive containing device code object files can be passed to clang command line for linking. For each given offload target it creates a device specific archives which is either passed to llvm-link if the target is amdgpu, or to clang-nvlink-wrapper if the target is nvptx. -L/-l flags are used to specify these fat archives on the command line. E.g. clang++ -fopenmp -fopenmp-targets=nvptx64 main.cpp -L. -lmylib It currently doesn't support linking an archive directly, like: clang++ -fopenmp -fopenmp-targets=nvptx64 main.cpp libmylib.a Linking with x86 offload also does not work. Reviewed By: ye-luo Differential Revision: https://reviews.llvm.org/D105191
-
Michał Górny authored
Replace separate read and write NativeFile instances with a single instance shared for reading and writing. There is no clear indication why two instances were used in the first place, and replacing them with just one does not seem to cause any regressions in tests or manual 'process connect file://...'. Differential Revision: https://reviews.llvm.org/D111314
-
Florian Hahn authored
Precommit test cases for D108114.
-
Frederic Cambus authored
Differential Revision: https://reviews.llvm.org/D111340
-