| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Reapply "[Support] Remove terminfo dependency (#92865)" (#93889) This reverts commit fe82a3da36196157c0caa1ef2505186782f750d1. This broke LLDB on MacOS due to a missing symbol during linking. The fix has been applied in c6c08eee37bada190bd1aa4593c88a5e2c8cdaac. Original commit message: The terminfo dependency introduces a significant nonhermeticity into the build. It doesn't respect --no-undefined-version meaning that it's not a dependency that can be built with Clang 17+. This forces maintainers of source-based distributions to implement patches or ignore linker errors. Remove it to reduce the closure size and improve portability of LLVM-based tools. Users can still use command line arguments to toggle color support expliticly. Fixes #75490 Closes #53294 #23355 | 2 年前 | |
| 1 年前 | ||
[bazel] format bazel files NFC | 2 年前 | |
Revert "demangle function names in trace files (#87626)" This reverts commit 0fa20c55b58deb94090985a5c5ffda4d5ceb3cd1. Storing raw symbol names is generally preferred in profile files. Demangling might lose information. Language frontends might use demangling schemes not supported by LLVMDemangle (https://github.com/llvm/llvm-project/issues/45901#issuecomment-2008686663). In addition, calling demangle for each function has a significant performance overhead (#102222). I believe that even if we decide to provide a producer-side demangling, it would not be on by default. Pull Request: https://github.com/llvm/llvm-project/pull/102274 (cherry picked from commit 72b73e23b6c36537db730ebea00f92798108a6e5) | 1 年前 | |
Introduce a Bazel build configuration This patch introduces configuration for a Bazel BUILD in a side directory in the monorepo. This is following the approval of https://github.com/llvm/llvm-www/blob/main/proposals/LP0002-BazelBuildConfiguration.md As detailed in the README, the Bazel BUILD is not supported by the community in general, and is maintained only by interested parties. It follows the requirements of the LLVM peripheral tier: https://llvm.org/docs/SupportPolicy.html#peripheral-tier. This is largely copied from https://github.com/google/llvm-bazel, with a few filepath tweaks and the addition of the README. Reviewed By: echristo, keith, dblaikie, kuhar Differential Revision: https://reviews.llvm.org/D90352 | 4 年前 | |
[bazel][NFC] Replace @bazel_tools//src/conditions with equivalent @platforms rules Followup to D147354. Using src/conditions is discouraged in favor of using rules from the @platforms repository directly. This replaces three conditions: * @bazel_tools//src/conditions:windows -> @platforms//os:windows * @bazel_tools//src/conditions:darwin -> @platforms//os:macos * @bazel_tools//src/conditions:freebsd -> @platforms//os:freebsd llvm/config.bzl has a non-trivial OS+CPU selection config, so that is omitted from this patch. There is intentionally no equivalent for that in @platforms because every project will have their own opinions about what a platform is, and it is not feasible for the bazel selection list to include every possible combination. The recommended idiom there is for projects to define their own supported platforms list, e.g. in a separate BUILD file or platform mapping. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D147948 | 3 年前 | |
[Bazel] Use PACKAGE_VERSION for version string. This enables "-rc" suffix in release branches. (cherry picked from commit 25efb746d907ce0ffdd9195d191ff0f6944ea3ca) | 1 年前 | |
[llvm-driver] Add driver alias for c++filt (#92803) Similar to 9d955a63c7b0d2d547a63d4074e03cd5ebd1f162, this allows the driver to respond to c++filt. | 2 年前 | |
[bzl] Remove obsolete output_to_genfiles = True (#83944) The [bazel docs](https://bazel.build/rules/lib/globals/bzl#rule) discourage setting this. The comments about being necessary for headers or genrules seem to be obsolete, at least for the LLVM tree itself. The effect of this is that generated files will go to bazel-bin instead of bazel-genfiles. One external use was fixed here: https://github.com/google/jax/commit/32bb3b06132b4256cd8674fb98bce057dc968610. | 2 年前 | |
lit_test : check if there is already a deps key in kwargs (#87290) This change checks if there is already a deps key in kwargs and concatenate it to avoid multiple values for deps key argument. background: https://github.com/llvm/llvm-project/pull/87022 recently added explicit deps to the lit_test. This is causing StableHLO bazel build failures at https://github.com/openxla/stablehlo/actions/runs/8511888283/job/23312383380?pr=2147 Tested: local build run is successful | 2 年前 | |
[Bazel] Remove explicit relative_to_caller_repository This is the default and the argument is deprecated. The documentation indicating it's the default is only since 4.0 (https://docs.bazel.build/versions/4.0.0/skylark/lib/Label.html#Label), but looking at the code it has been the default since its introduction in https://bazel.googlesource.com/bazel/+/6f15335dea with Bazel 0.2.1 (https://bazel.googlesource.com/bazel/+show/0.2.1/CHANGELOG.md) Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D106411 | 4 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 1 年前 | ||
| 4 年前 | ||
| 3 年前 | ||
| 1 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 2 年前 | ||
| 4 年前 |