- May 28, 2023
-
-
Krzysztof Parzyszek authored
Vector length depends on the HVX mode, so make the size and offset unknown instead using values for some specific mode.
-
Justin Lebar authored
Previously we used the later of GEPA or GEPB. This is hacky because really we should be using the later of the two load/store instructions being considered. But also it's flat-out incorrect, because GEPA and GEPB might be in different BBs, in which case we cannot ask which one comes last (assertion failure, https://reviews.llvm.org/D149893#4378332). Fixed, now we use the correct context instruction. Differential Revision: https://reviews.llvm.org/D151630
-
Vlad Serebrennikov authored
This changes a handful of recently implemented DRs from "unreleased" to "full" styling in cxx_dr_status.html
-
Ivan Murashko authored
Previously, if a header was found via in a header map, and not just remapped. we wouldn't also find the module it maps to when using implicit modules (for module maps that were explicitly loaded). This diff just updates these code paths to also locate the owning module via `findUsableModuleForHeader`. Reviewed By: benlangmuir Differential Revision: https://reviews.llvm.org/D103930
-
Martin Storsjö authored
Use ASSERT_WITH_OPERATOR_NEW_FALLBACKS where relevant to waive the known cases where operator new isn't overridden as expected, in MinGW DLL configurations. Clarify the reason for why the fallback in new.delete.array/new.size_align_nothrow.replace.indirect doesn't work as expected, which can be considered a vcruntime bug. Differential Revision: https://reviews.llvm.org/D151304
-
Martin Storsjö authored
This fixes two issues that are observed after 5111286f: For builds with GCC with LLVM_LINK_LLVM_DYLIB=ON, we previously got build errors, as libclang-cpp.dll suddenly only contained the functions that were marked dllexport via REPL_EXTERNAL_VISIBILITY, instead of all symbols as expected. For MinGW builds with Clang, building previously succeeded (as it used either the __attribute__((visibility("default"))) annotation or nothing at all), and the functions were exported from libclang-cpp.dll if that was built, but the unit test failed (as neither of those cases made the functions exported from an EXE). Don't use the visibility attributes on MinGW targets for these purposes; setting default visibility only makes a difference if building with e.g. -fvisibility=hidden, but it doesn't make the symbols exported from an EXE. Differential Revision: https://reviews.llvm.org/D151620
-
eopXD authored
Signed-off by: eop Chen <eop.chen@sifive.com>
-
Kazu Hirata authored
The module inliner has its own logic in deciding the order in which call sites are inlined, so the comment is inapplicable.
-
Kazu Hirata authored
The corresponding function definition was removed by: commit 55662b24 Author: Balazs Benics <balazs.benics@sigmatechnology.se> Date: Thu Jul 1 10:54:28 2021 +0200
-
Kazu Hirata authored
The corresponding definition was removed by: commit a84374dc Author: Artem Dergachev <artem.dergachev@gmail.com> Date: Thu Jun 14 01:40:49 2018 +0000
-
Kazu Hirata authored
The corresponding function definition was removed by: commit e0fb481c Author: Artem Dergachev <artem.dergachev@gmail.com> Date: Fri May 4 23:01:10 2018 +0000
-
Aart Bik authored
Reviewed By: K-Wu Differential Revision: https://reviews.llvm.org/D151619
-
Eugene Burmako authored
Reviewed By: aartbik Differential Revision: https://reviews.llvm.org/D151618
-
Kun Wu authored
Differential Revision: https://reviews.llvm.org/D151279
-
Eugene Burmako authored
This patch normalizes formatting of the the root BUILD.bazel file by: 1) adjusting indentation a little bit, 2) alphabetically ordering dependencies. These small deviations were introduced by some yesterday's patches: * https://reviews.llvm.org/D151104 * https://reviews.llvm.org/D151346 * https://reviews.llvm.org/rG16fe2b37365c00b0c6d0ed22c2e6521f2d5de01a * https://reviews.llvm.org/rG4d1cd1d8caab13d6b76ce6fc4ff76a01a7931c34 Reviewed By: aartbik Differential Revision: https://reviews.llvm.org/D151499
-
Florian Hahn authored
Add initial set of tests for improved loop phi handling.
-
LLVM GN Syncbot authored
-
Nico Weber authored
-
Kazu Hirata authored
The declaration was added without a corresponding function definition by: commit ae497ded Author: DeLesley Hutchins <delesley@google.com> Date: Sat Apr 19 00:35:54 2014 +0000
-
Kazu Hirata authored
The corresponding function body was removed by: commit 925296b4 Author: Douglas Gregor <dgregor@apple.com> Date: Tue Jul 19 16:10:42 2011 +0000
-
Kazu Hirata authored
The last use was removed by: commit 0eb06cb3 Author: Roy Jacobson <roi.jacobson1@gmail.com> Date: Tue Mar 14 21:25:54 2023 +0200 Differential Revision: https://reviews.llvm.org/D151607
-
Kazu Hirata authored
-
Kazu Hirata authored
-
Krzysztof Parzyszek authored
-
- May 27, 2023
-
-
Bing1 Yu authored
class InstructionRemover manages resources such as dynamically allocated memory, it's generally a good practice to either implement a custom copy constructor or disable the default one. Reviewed By: pengfei Differential Revision: https://reviews.llvm.org/D151543
-
Manna, Soumi authored
This patch adds an assert. Reviewed By: erichkeane Differential Revision: https://reviews.llvm.org/D151480
-
Simon Pilgrim authored
Noticed in D150143/D150526 - we currently create scalar Constant values using the broadcast instruction width, which might be wider than the original build vector width, making it tricky to recognise the original constant bits data. If we have widened the broadcast value, its much more useful for asm comments if we create a ConstantVector with the original element data, add that to the constant-pool and load that with the same (wider) broadcast instruction.
-
Markus Mützel authored
If the path to the TEMP folder contains (non-ASCII) characters that cannot be encoded in the current 8-bit locale of the user, openfile_mkstemp might fail on Windows. That is an unlikely scenario. But given that the path to the default TEMP folder on Windows contains the Windows user name, it is still possible. Use the wide character Windows API to avoid that (unlikely) issue. Reviewed By: vzakhari Differential Revision: https://reviews.llvm.org/D151571
-
Mark de Wever authored
These tests pass on Windows without additional changes. This has been tested in D150593.
-
Mark de Wever authored
This reverts commit d763c6e5. Adds the patch by @hans from https://github.com/llvm/llvm-project/issues/62719 This patch fixes the Windows build. d763c6e5 reverted the reviews D144509 [CMake] Bumps minimum version to 3.20.0. This partly undoes D137724. This change has been discussed on discourse https://discourse.llvm.org/t/rfc-upgrading-llvms-minimum-required-cmake-version/66193 Note this does not remove work-arounds for older CMake versions, that will be done in followup patches. D150532 [OpenMP] Compile assembly files as ASM, not C Since CMake 3.20, CMake explicitly passes "-x c" (or equivalent) when compiling a file which has been set as having the language C. This behaviour change only takes place if "cmake_minimum_required" is set to 3.20 or newer, or if the policy CMP0119 is set to new. Attempting to compile assembly files with "-x c" fails, however this is workarounded in many c...
-
Benjamin Kramer authored
-
M. Zeeshan Siddiqui authored
Fix indentation and spacing. Reviewed By: pengfei Differential Revision: https://reviews.llvm.org/D151610
-
Anubhab Ghosh authored
CUDA support can be enabled in clang-repl with --cuda flag. Device code linking is not yet supported. inline must be used with all __device__ functions. Differential Revision: https://reviews.llvm.org/D146389
-
Haojian Wu authored
attempt.
-
Haojian Wu authored
-
M. Zeeshan Siddiqui authored
[Clang][BFloat16] Upgrade __bf16 to arithmetic type, change mangling, and extend excess precision support Pursuant to discussions at https://discourse.llvm.org/t/rfc-c-23-p1467r9-extended-floating-point-types-and-standard-names/70033/22, this commit enhances the handling of the __bf16 type in Clang. - Firstly, it upgrades __bf16 from a storage-only type to an arithmetic type. - Secondly, it changes the mangling of __bf16 to DF16b on all architectures except ARM. This change has been made in accordance with the finalization of the mangling for the std::bfloat16_t type, as discussed at https://github.com/itanium-cxx-abi/cxx-abi/pull/147. - Finally, this commit extends the existing excess precision support to the __bf16 type. This applies to hardware architectures that do not natively support bfloat16 arithmetic. Appropriate tests have been added to verify the effects of these changes and ensure no regressions in other areas of the compiler. Reviewed By: rjmccall, pengfei, zahiraam Differential Revision: https://reviews.llvm.org/D150913
-
Sergei Barannikov authored
The last use was removed by commit 48b185d6 Author: Dan Gohman <gohman@apple.com> Date: Fri Sep 25 20:36:54 2009 +0000
-
Kazu Hirata authored
The corresponding function definition was removed by: commit 93d7002d Author: Corentin Jabot <corentinjabot@gmail.com> Date: Sun Feb 6 22:58:43 2022 +0100
-
Kazu Hirata authored
The corresponding function definition was removed by: commit 1a929525 Author: Kadir Cetinkaya <kadircet@google.com> Date: Tue Dec 21 17:06:40 2021 +0100
-
Kazu Hirata authored
The corresponding function definitions were removed by: commit a2dbfb6b Author: Giorgis Georgakoudis <georgakoudis1@llnl.gov> Date: Wed Apr 21 11:41:31 2021 -0700
-