- Aug 01, 2023
-
-
Kazu Hirata authored
The last use was removed by: commit 6b31e63b Author: Kazu Hirata <kazu@google.com> Date: Sat Jun 24 07:33:50 2023 -0700
-
Christian Kandeler authored
It's valuable to have document highlights for labels and be able to find references to them. Reviewed By: nridge Differential Revision: https://reviews.llvm.org/D150124
-
Nikita Popov authored
This reverts commit 3e386b22. Next to the original fold, this also implements an unnecessary and inappropriate simplifyICmpWithDominatingAssume() based fold.
-
Jay Foad authored
This adds support for reprocessing new instructions that were generated by the target's eliminateFrameIndex. Backwards frame index elimination uses backwards register scavenging, which is preferred because it does not rely on accurate kill flags. Differential Revision: https://reviews.llvm.org/D156690
-
Martin Storsjö authored
This adds notes for the change from https://reviews.llvm.org/D146398 / fcbbd964. Differential Revision: https://reviews.llvm.org/D156627
-
Erick Velez authored
Differential Revision: https://reviews.llvm.org/D154038
-
LLVM GN Syncbot authored
-
Jun Sha (Joshua) authored
The RISC-V psABI recently added __bf16 in https://github.com/riscv-non-isa/riscv-elf-psabi-doc/pull/367. Now we can enable this new type in clang. Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D150929
-
Sameer Sahasrabuddhe authored
The refactored template can now be used with MachineVerifier. Reviewed By: arsenm Differential Revision: https://reviews.llvm.org/D156522
-
Yeting Kuo authored
Previously when llvm.reduce.* lowered, riscv backend created scalar vector with netural element as start value. For llvm.reduce.and/or/min/max/fmax/fmin, we could use the first element of source as the start value. It's benefit for RVV since we could just use source vector as start vector. Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D155929
-
Zhongyunde authored
We check the loop trip count is known a power of 2 to determine whether the tail loop can be eliminated in D146199. However, the remainder loop of mask scalable loop can also be removed If we know the mask is always going to be true for every vector iteration. Depend on the assume of power-of-two vscale on D155350 proofs: https://alive2.llvm.org/ce/z/FkTMoy Fix https://github.com/llvm/llvm-project/issues/63616. Reviewed By: goldstein.w.n, nikic, david-arm, paulwalker-arm Differential Revision: https://reviews.llvm.org/D154953
-
Zhongyunde authored
Differential Revision: https://reviews.llvm.org/D156591
-
Jun Sha (Joshua) authored
Currentlt, bf16 operations are automatically supported by promoting to float. This patch adds bf16 support by ensuring that load extension / truncate store operations are properly expanded. Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D156646
-
Tamir Duberstein authored
-
Nikolas Klauser authored
Reviewed By: #libc, ldionne Spies: wangpc, libcxx-commits Differential Revision: https://reviews.llvm.org/D155512
-
Chuanqi Xu authored
This reverts commit 77ef88d7. There is an unimaged crash report after landing this. See https://reviews.llvm.org/D154695.
-
Nikolas Klauser authored
Reviewed By: #libc, Mordante Spies: Mordante, libcxx-commits Differential Revision: https://reviews.llvm.org/D155325
-
Alexander Yermolovich authored
Limiting the test to only X86. Reviewed By: Amir Differential Revision: https://reviews.llvm.org/D156765
-
Craig Topper authored
-
LLVM GN Syncbot authored
-
LLVM GN Syncbot authored
-
Nikolas Klauser authored
Reviewed By: #libc, Mordante Spies: arichardson, Mordante, libcxx-commits Differential Revision: https://reviews.llvm.org/D155260
-
Nikolas Klauser authored
Reviewed By: #libc, Mordante Spies: Mordante, libcxx-commits Differential Revision: https://reviews.llvm.org/D155259
-
Nikolas Klauser authored
Reviewed By: #libc, Mordante Spies: Mordante, arichardson, libcxx-commits Differential Revision: https://reviews.llvm.org/D155258
-
Matt Arsenault authored
This reverts commit a496c8be. The workaround in c26dfc81 should work around the underlying problem with SUBREG_TO_REG.
-
Jakub Kuderski authored
Handle both v0 and v1 operands that may be converted to SPIR-V scalars. Fixes: https://github.com/llvm/llvm-project/issues/64271 Reviewed By: antiagainst Differential Revision: https://reviews.llvm.org/D156717
-
Alexander Yermolovich authored
Clang can generate DW_TAG_inlined_subroutine with low_pc 0. With split dwarf this led to range offset being a negative number. Reviewed By: maksfb Differential Revision: https://reviews.llvm.org/D156742
-
wren romano authored
Depends On D156001 Reviewed By: aartbik Differential Revision: https://reviews.llvm.org/D156010
-
Steven Wu authored
This reverts commit c56514f2. This commit adds global state that is shared between clang driver and clang cc1, which is not correct when clang is used with `-fno-integrated-cc1` option (no integrated cc1). The -march and -mtune option needs to be properly passed through cc1 command-line and stored in TargetInfo.
-
Roland McGrath authored
This prevents -Wmissing-braces warnings. Reviewed By: michaelrj, Caslyn Differential Revision: https://reviews.llvm.org/D156629
-
Matt Arsenault authored
This should be approximately first and run with other module passes. https://reviews.llvm.org/D155987
-
Matt Arsenault authored
-
Amir Ayupov authored
BOLT-ERROR and BOLT-WARNING messages are output to stderr which is not captured by piping to FileCheck. Redirect stderr to stdout to fix that in tests. Reviewed By: #bolt, maksfb Differential Revision: https://reviews.llvm.org/D156340
-
Matt Arsenault authored
Don't understand why this would either be OK or necessary, but doesn't appear to happen in any tests. This was introduced way back in 76e66c31 https://reviews.llvm.org/D156265
-
Matt Arsenault authored
For the purpose of the test it works as well to have a use after the copy itself.
-
Matt Arsenault authored
-
Peter Klausler authored
This gets our -Werror build working again. Differential Revision: https://reviews.llvm.org/D156745
-
Alexey Bader authored
Compile units are not left explicitly if they have const global expression. They should be left if that const global is used in a function that is contained in extracted module. Signed-off-by:
Mikhail Lychkov <mikhail.lychkov@intel.com> Differential Revision: https://reviews.llvm.org/D131179
-
Johannes Doerfert authored
The test run fine on my AMD GPU machine, we should verify them on others too and put them into our regular testing. Not testing O1/2/3 is really bad and not testing all architecturs is similarly problematic. Differential Revision: https://reviews.llvm.org/D148576
-
Johannes Doerfert authored
-