Revision tags: llvmorg-17.0.0-rc4, llvmorg-17.0.0-rc3, llvmorg-17.0.0-rc2, llvmorg-17.0.0-rc1, llvmorg-18-init |
|
#
53b6a169 |
| 21-Jul-2023 |
Nathan Gauër <brioche@google.com> |
[SPIR-V] Add SPIR-V logical triple.
Clang implements SPIR-V with both Physical32 and Physical64 addressing models. This commit adds a new triple value for the Logical addressing model.
Differential
[SPIR-V] Add SPIR-V logical triple.
Clang implements SPIR-V with both Physical32 and Physical64 addressing models. This commit adds a new triple value for the Logical addressing model.
Differential Revision: https://reviews.llvm.org/D155978
show more ...
|
#
9f77facf |
| 10-Sep-2023 |
Fangrui Song <i@maskray.me> |
[Driver] Properly report error for unsupported powerpc darwin/macos triples
The removal started at https://reviews.llvm.org/D50989 and https://reviews.llvm.org/D75494 removed the Triple support. Wit
[Driver] Properly report error for unsupported powerpc darwin/macos triples
The removal started at https://reviews.llvm.org/D50989 and https://reviews.llvm.org/D75494 removed the Triple support. Without recognizing Darwin triples as Mach-O, we will get assertion error in ToolChains/Darwin.h due to the universal binary mechanism.
Fix #47698
show more ...
|
#
5165593a |
| 27-Aug-2023 |
Brad Smith <brad@comstyle.com> |
Delete CloudABI support
After this D108637 and with FreeBSD -current and now 14 dropping support for CloudABI I think it is time to consider deleting the CloudABI support.
Reviewed By: MaskRay
Dif
Delete CloudABI support
After this D108637 and with FreeBSD -current and now 14 dropping support for CloudABI I think it is time to consider deleting the CloudABI support.
Reviewed By: MaskRay
Differential Revision: https://reviews.llvm.org/D158920
show more ...
|
#
2a105105 |
| 27-Aug-2023 |
Brad Smith <brad@comstyle.com> |
Delete Ananas support
After looking at this further I think the Ananas support should be removed.
They stopped using Clang. There have never been any releases either; as in source only, and the bac
Delete Ananas support
After looking at this further I think the Ananas support should be removed.
They stopped using Clang. There have never been any releases either; as in source only, and the backend is not maintained.
Reviewed By: MaskRay
Differential Revision: https://reviews.llvm.org/D158946
show more ...
|
#
24eaf785 |
| 25-Aug-2023 |
Brad Smith <brad@comstyle.com> |
Cleanup remaining bits for Minix, Contiki and Myriad
Reviewed By: MaskRay
Differential Revision: https://reviews.llvm.org/D158806
|
#
a926a266 |
| 17-Jul-2023 |
Weining Lu <luweining@loongson.cn> |
[Triple] Add llvm::Triple::isLoongArch{32,64}
Reviewed By: MaskRay
Differential Revision: https://reviews.llvm.org/D155163
|
Revision tags: llvmorg-16.0.6 |
|
#
30198bd7 |
| 06-Jun-2023 |
prabhukr <prabhukr@google.com> |
[Triple] Add triple for UEFI
Target triple to support "x86_64-unknown-uefi"
Reviewed By: phosek
Differential Revision: https://reviews.llvm.org/D131594
|
Revision tags: llvmorg-16.0.5, llvmorg-16.0.4, llvmorg-16.0.3, llvmorg-16.0.2 |
|
#
887d6ab1 |
| 16-Apr-2023 |
Lang Hames <lhames@gmail.com> |
[TargetParser] Expose Triple::getObjectFormatTypeName.
This is useful for printing the object format of a triple in debug logs.
|
Revision tags: llvmorg-16.0.1, llvmorg-16.0.0, llvmorg-16.0.0-rc4 |
|
#
c417b7a6 |
| 27-Feb-2023 |
Pavel Kosov <kpdev42@gmail.com> |
[OHOS] Add support for OpenHarmony
Add support for OpenHarmony OS
General OpenHarmony OS discussion on discourse thread "[RFC] Add support for OpenHarmony OS" https://discourse.llvm.org/t/rfc-add-s
[OHOS] Add support for OpenHarmony
Add support for OpenHarmony OS
General OpenHarmony OS discussion on discourse thread "[RFC] Add support for OpenHarmony OS" https://discourse.llvm.org/t/rfc-add-support-for-openharmony-os/66656
Reviewed By: DavidSpickett
Differential Revision: https://reviews.llvm.org/D138202
show more ...
|
Revision tags: llvmorg-16.0.0-rc3, llvmorg-16.0.0-rc2, llvmorg-16.0.0-rc1, llvmorg-17-init, llvmorg-15.0.7 |
|
#
8c618e8f |
| 26-Dec-2022 |
Andrei Safronov <andrei.safronov@espressif.com> |
[Xtensa 1/10] Recognize Xtensa in triple parsing code
I'm sharing initial set of patches that adds LLVM backend for Xtensa architecture. It is based on this LLVM fork https://github.com/espressif/ll
[Xtensa 1/10] Recognize Xtensa in triple parsing code
I'm sharing initial set of patches that adds LLVM backend for Xtensa architecture. It is based on this LLVM fork https://github.com/espressif/llvm-xtensa. I prepared patches by similar way like it was already successfully done for RISCV, i.e. incrementally add an initial MC layer for Xtensa by small chunks which could be reviewable.
Differential Revision: https://reviews.llvm.org/D64826
show more ...
|
#
f09cf34d |
| 20-Dec-2022 |
Archibald Elliott <archibald.elliott@arm.com> |
[Support] Move TargetParsers to new component
This is a fairly large changeset, but it can be broken into a few pieces: - `llvm/Support/*TargetParser*` are all moved from the LLVM Support componen
[Support] Move TargetParsers to new component
This is a fairly large changeset, but it can be broken into a few pieces: - `llvm/Support/*TargetParser*` are all moved from the LLVM Support component into a new LLVM Component called "TargetParser". This potentially enables using tablegen to maintain this information, as is shown in https://reviews.llvm.org/D137517. This cannot currently be done, as llvm-tblgen relies on LLVM's Support component. - This also moves two files from Support which use and depend on information in the TargetParser: - `llvm/Support/Host.{h,cpp}` which contains functions for inspecting the current Host machine for info about it, primarily to support getting the host triple, but also for `-mcpu=native` support in e.g. Clang. This is fairly tightly intertwined with the information in `X86TargetParser.h`, so keeping them in the same component makes sense. - `llvm/ADT/Triple.h` and `llvm/Support/Triple.cpp`, which contains the target triple parser and representation. This is very intertwined with the Arm target parser, because the arm architecture version appears in canonical triples on arm platforms. - I moved the relevant unittests to their own directory.
And so, we end up with a single component that has all the information about the following, which to me seems like a unified component: - Triples that LLVM Knows about - Architecture names and CPUs that LLVM knows about - CPU detection logic for LLVM
Given this, I have also moved `RISCVISAInfo.h` into this component, as it seems to me to be part of that same set of functionality.
If you get link errors in your components after this patch, you likely need to add TargetParser into LLVM_LINK_COMPONENTS in CMake.
Differential Revision: https://reviews.llvm.org/D137838
show more ...
|