intel/llvm
1
0
Fork 0
mirror of https://github.com/intel/llvm.git synced 2026-01-25 10:55:58 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
4091f4dd96d1501e007ed044fc93be1bfaafea08
llvm/utils/bazel/WORKSPACE

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

193 lines
6.6 KiB
Python
Raw Normal View History

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
2021-05-18 15:42:25 -07:00
# This file is licensed under the Apache License v2.0 with LLVM Exceptions.
# See https://llvm.org/LICENSE.txt for license information.
# SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
load("@bazel_tools//tools/build_defs/repo:utils.bzl", "maybe")
[bazel] Add rules for clang-fuzzer protobuf-related libraries (#123126) Also bumped up bazel_skylib to the latest version because the proto rules were complaining about a missing feature.
2025-01-16 10:12:46 -08:00
SKYLIB_VERSION = "1.7.1"
[Bazel] Use bazel_skylib paths for paths munging We do a lot of path munging and bazel_sklyib is a pretty reasonable dep. Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D106175
2021-07-16 11:49:50 -07:00
http_archive(
name = "bazel_skylib",
[bazel] Add rules for clang-fuzzer protobuf-related libraries (#123126) Also bumped up bazel_skylib to the latest version because the proto rules were complaining about a missing feature.
2025-01-16 10:12:46 -08:00
sha256 = "bc283cdfcd526a52c3201279cda4bc298652efa898b10b4db0837dc51652756f",
[Bazel] Use bazel_skylib paths for paths munging We do a lot of path munging and bazel_sklyib is a pretty reasonable dep. Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D106175
2021-07-16 11:49:50 -07:00
urls = [
[NFC] Reformat bzl files with buildifier
2024-02-12 11:35:17 -08:00
"https://mirror.bazel.build/github.com/bazelbuild/bazel-skylib/releases/download/{version}/bazel-skylib-{version}.tar.gz".format(version = SKYLIB_VERSION),
"https://github.com/bazelbuild/bazel-skylib/releases/download/{version}/bazel-skylib-{version}.tar.gz".format(version = SKYLIB_VERSION),
[Bazel] Use bazel_skylib paths for paths munging We do a lot of path munging and bazel_sklyib is a pretty reasonable dep. Reviewed By: jpienaar Differential Revision: https://reviews.llvm.org/D106175
2021-07-16 11:49:50 -07:00
],
)
[bazel] update .bazelversion to 8.0.0 (#119425) Fixes: ERROR: The project you're trying to build requires Bazel 7.3.0 (specified in llvm-project/utils/bazel/.bazelversion), but it wasn't found in /usr/bin. You can install the required Bazel version via apt: sudo apt update && sudo apt install bazel-7.3.0 If this doesn't work, check Bazel's installation instructions for help: https://bazel.build/install/ubuntu Link: https://blog.bazel.build/2024/12/09/bazel-8-release.html
2024-12-10 13:07:52 -08:00
http_archive(
name = "rules_cc",
sha256 = "abc605dd850f813bb37004b77db20106a19311a96b2da1c92b789da529d28fe1",
strip_prefix = "rules_cc-0.0.17",
[bazel] Add rules for clang-fuzzer protobuf-related libraries (#123126) Also bumped up bazel_skylib to the latest version because the proto rules were complaining about a missing feature.
2025-01-16 10:12:46 -08:00
urls = ["https://github.com/bazelbuild/rules_cc/releases/download/0.0.17/rules_cc-0.0.17.tar.gz"],
[bazel] update .bazelversion to 8.0.0 (#119425) Fixes: ERROR: The project you're trying to build requires Bazel 7.3.0 (specified in llvm-project/utils/bazel/.bazelversion), but it wasn't found in /usr/bin. You can install the required Bazel version via apt: sudo apt update && sudo apt install bazel-7.3.0 If this doesn't work, check Bazel's installation instructions for help: https://bazel.build/install/ubuntu Link: https://blog.bazel.build/2024/12/09/bazel-8-release.html
2024-12-10 13:07:52 -08:00
)
Simplify setting up LLVM as bazel external repo Only require one intermediate repository instead of two. Fewer parameters in llvm_config. Second attempt of https://reviews.llvm.org/D107714, this time also updating `third_party_build` and `deps_impl` paths. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D108274
2021-08-18 09:14:42 +02:00
new_local_repository(
name = "llvm-raw",
build_file_content = "# empty",
[bazel] Restore libpfm as a conditional dependency for exegesis. We used to have `pfm` built into exegesis, although since it's an external dependency we marked it as a manual target. Because of this we didn't have buildbot coverage and so we removed it in D134510 after we had a few breakages that weren't caught. This adds it back, but with three possible states similar to the story with `mpfr`, i.e. it can either be disabled, built from external sources (git/make), or use whatever `-lpfm` is installed on the system. This change is modeled after D119547. Like that patch, the default is off (matching the status quo), but unlike that patch we don't enable it for CI because IIRC we don't have the package installed there, and building from source might be expensive. We could enable it later either after installing it on buildbot machines or by measuring build cost and deeming it OK. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D138470
2022-12-28 08:13:20 -08:00
path = "../../",
Revert "Simplify setting up LLVM as bazel external repo" This breaks the rules for creating repository dependencies when invoked from another workspace. See comment on https://reviews.llvm.org/D107714 This reverts commit 934f084ad42231d225bd0eee3342f4b5f7e1ce6e. Differential Revision: https://reviews.llvm.org/D108245
2021-08-17 14:45:43 -07:00
)
Simplify setting up LLVM as bazel external repo Only require one intermediate repository instead of two. Fewer parameters in llvm_config. Remove bazel_skylib dependency. Reviewed By: goncharov Differential Revision: https://reviews.llvm.org/D107714
2021-08-08 15:19:33 +02:00
Simplify setting up LLVM as bazel external repo Only require one intermediate repository instead of two. Fewer parameters in llvm_config. Second attempt of https://reviews.llvm.org/D107714, this time also updating `third_party_build` and `deps_impl` paths. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D108274
2021-08-18 09:14:42 +02:00
load("@llvm-raw//utils/bazel:configure.bzl", "llvm_configure")
llvm_configure(name = "llvm-project")
[bazel] Add support for pybind (#98398) Previously these targets were disabled, but with a relatively new rules_python we can build these pointing at a hermetic python, which allows us to build these safely. Users can still access the files directly if they need to customize how these are built.
2024-07-18 17:23:02 -07:00
maybe(
http_archive,
name = "rules_python",
[bazel] update .bazelversion to 8.0.0 (#119425) Fixes: ERROR: The project you're trying to build requires Bazel 7.3.0 (specified in llvm-project/utils/bazel/.bazelversion), but it wasn't found in /usr/bin. You can install the required Bazel version via apt: sudo apt update && sudo apt install bazel-7.3.0 If this doesn't work, check Bazel's installation instructions for help: https://bazel.build/install/ubuntu Link: https://blog.bazel.build/2024/12/09/bazel-8-release.html
2024-12-10 13:07:52 -08:00
sha256 = "4f7e2aa1eb9aa722d96498f5ef514f426c1f55161c3c9ae628c857a7128ceb07",
strip_prefix = "rules_python-1.0.0",
url = "https://github.com/bazelbuild/rules_python/releases/download/1.0.0/rules_python-1.0.0.tar.gz",
[bazel] Add support for pybind (#98398) Previously these targets were disabled, but with a relatively new rules_python we can build these pointing at a hermetic python, which allows us to build these safely. Users can still access the files directly if they need to customize how these are built.
2024-07-18 17:23:02 -07:00
)
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
2021-05-18 15:42:25 -07:00
maybe(
http_archive,
[bazel] Rework zlib dependency Switches the library to use the zlib-ng implementation since the original implementation is warning-incompatible with recent versions of clang. Removes the wrapper logic for zlib in the bazel build and introduces new logic to handle `LLVM_ENABLE_ZLIB`. Removes the `BAZEL_LLVM_ZLIB_STRATEGY` environment variable and instead introduces a boolean `--@llvm_zlib//:llvm_enable_zlib` flag which defaults to true. To migrate: * The previous "external" strategy is the default. May be explicitly enabled with `--@llvm_zlib//:llvm_enable_zlib=true`. For custom zlib variants you can use the BUILD file at `third_party_build/zlib.BUILD` as reference and adjust the `@llvm_zlib` archive in the `WORKSPACE` directly. * The previous "disable" strategy may be enabled with `--@llvm_zlib//:llvm_enable_zlib=false`. * The previous "system" strategy has been removed since it breaks hermeticity. If you need the "system" setup, use the "external" strategy and override the zlib dependency. Addresses breakages of downstream projects using upstream clang and the previously "external" zlib strategy (D141553). Reviewed By: MaskRay, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D143320
2023-05-19 23:03:46 +02:00
name = "llvm_zlib",
build_file = "@llvm-raw//utils/bazel/third_party_build:zlib-ng.BUILD",
sha256 = "e36bb346c00472a1f9ff2a0a4643e590a254be6379da7cddd9daeb9a7f296731",
strip_prefix = "zlib-ng-2.0.7",
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
2021-05-18 15:42:25 -07:00
urls = [
[bazel] Rework zlib dependency Switches the library to use the zlib-ng implementation since the original implementation is warning-incompatible with recent versions of clang. Removes the wrapper logic for zlib in the bazel build and introduces new logic to handle `LLVM_ENABLE_ZLIB`. Removes the `BAZEL_LLVM_ZLIB_STRATEGY` environment variable and instead introduces a boolean `--@llvm_zlib//:llvm_enable_zlib` flag which defaults to true. To migrate: * The previous "external" strategy is the default. May be explicitly enabled with `--@llvm_zlib//:llvm_enable_zlib=true`. For custom zlib variants you can use the BUILD file at `third_party_build/zlib.BUILD` as reference and adjust the `@llvm_zlib` archive in the `WORKSPACE` directly. * The previous "disable" strategy may be enabled with `--@llvm_zlib//:llvm_enable_zlib=false`. * The previous "system" strategy has been removed since it breaks hermeticity. If you need the "system" setup, use the "external" strategy and override the zlib dependency. Addresses breakages of downstream projects using upstream clang and the previously "external" zlib strategy (D141553). Reviewed By: MaskRay, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D143320
2023-05-19 23:03:46 +02:00
"https://github.com/zlib-ng/zlib-ng/archive/refs/tags/2.0.7.zip",
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
2021-05-18 15:42:25 -07:00
],
)
maybe(
http_archive,
name = "vulkan_headers",
Simplify setting up LLVM as bazel external repo Only require one intermediate repository instead of two. Fewer parameters in llvm_config. Second attempt of https://reviews.llvm.org/D107714, this time also updating `third_party_build` and `deps_impl` paths. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D108274
2021-08-18 09:14:42 +02:00
build_file = "@llvm-raw//utils/bazel/third_party_build:vulkan_headers.BUILD",
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
2021-05-18 15:42:25 -07:00
sha256 = "19f491784ef0bc73caff877d11c96a48b946b5a1c805079d9006e3fbaa5c1895",
strip_prefix = "Vulkan-Headers-9bd3f561bcee3f01d22912de10bb07ce4e23d378",
urls = [
"https://github.com/KhronosGroup/Vulkan-Headers/archive/9bd3f561bcee3f01d22912de10bb07ce4e23d378.tar.gz",
],
)
Simplify setting up LLVM as bazel external repo Only require one intermediate repository instead of two. Fewer parameters in llvm_config. Second attempt of https://reviews.llvm.org/D107714, this time also updating `third_party_build` and `deps_impl` paths. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D108274
2021-08-18 09:14:42 +02:00
load("@llvm-raw//utils/bazel:vulkan_sdk.bzl", "vulkan_sdk_setup")
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
2021-05-18 15:42:25 -07:00
maybe(
vulkan_sdk_setup,
name = "vulkan_sdk",
)
[bazel] Codesign debugserver on macOS (#91789) This tool doesn't work unless it's signed with the entitlements used here. We should probably consider using the macos_command_line_application rule from rules_apple which manages this more flexibly for us, but for now this works. This uses apple_genrule as opposed to genrule since the former encodes the Xcode environment info into the action so it is correctly invalidated if that changes.
2024-05-10 14:20:09 -07:00
http_archive(
name = "build_bazel_apple_support",
sha256 = "c4bb2b7367c484382300aee75be598b92f847896fb31bbd22f3a2346adf66a80",
url = "https://github.com/bazelbuild/apple_support/releases/download/1.15.1/apple_support.1.15.1.tar.gz",
)
load(
"@build_bazel_apple_support//lib:repositories.bzl",
"apple_support_dependencies",
)
apple_support_dependencies()
[reland][libc][bazel] Add tests to the bazel build This patch adds bazel tests for llvm-libc. Some math tests rely on the `mpfr` library. This is controlled via the `--@llvm-project//libc:libc_math_mpfr` flag. It can take three values: - `external` (default) will build `mpfr` and `gmp` from source. - `system` will use the system installed `mpfr` library. - `disable` will skip tests relying on `mpfr`. Reviewed By: sivachandra, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D119547
2022-11-18 10:14:37 +00:00
# llvm libc math tests reply on `mpfr`.
# The availability of `mpfr` is controlled by a flag and can be either `disable`, `system` or `external`.
# Continuous integration uses `system` to speed up the build process (see .bazelrc).
# Otherwise by default it is set to `external`: `mpfr` and `gmp` are built from source by using `rules_foreign_cc`.
# Note: that building from source requires `m4` to be installed on the host machine.
# This is a known issue: https://github.com/bazelbuild/rules_foreign_cc/issues/755.
[bazel] Replace git_repository with http_archive. (#99422) The current git_repository usage points to tags, which leads to warnings that the build may not be reproducable due to not using a git sha. The docs for [git_repository](https://bazel.build/rules/lib/repo/git#git_repository) recommend using `http_archive`, so switch to that instead. Also bump to newer versions for these two repos.
2024-07-18 21:56:37 -05:00
http_archive(
[reland][libc][bazel] Add tests to the bazel build This patch adds bazel tests for llvm-libc. Some math tests rely on the `mpfr` library. This is controlled via the `--@llvm-project//libc:libc_math_mpfr` flag. It can take three values: - `external` (default) will build `mpfr` and `gmp` from source. - `system` will use the system installed `mpfr` library. - `disable` will skip tests relying on `mpfr`. Reviewed By: sivachandra, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D119547
2022-11-18 10:14:37 +00:00
name = "rules_foreign_cc",
[bazel] Replace git_repository with http_archive. (#99422) The current git_repository usage points to tags, which leads to warnings that the build may not be reproducable due to not using a git sha. The docs for [git_repository](https://bazel.build/rules/lib/repo/git#git_repository) recommend using `http_archive`, so switch to that instead. Also bump to newer versions for these two repos.
2024-07-18 21:56:37 -05:00
sha256 = "4b33d62cf109bcccf286b30ed7121129cc34cf4f4ed9d8a11f38d9108f40ba74",
strip_prefix = "rules_foreign_cc-0.11.1",
url = "https://github.com/bazelbuild/rules_foreign_cc/releases/download/0.11.1/rules_foreign_cc-0.11.1.tar.gz",
[reland][libc][bazel] Add tests to the bazel build This patch adds bazel tests for llvm-libc. Some math tests rely on the `mpfr` library. This is controlled via the `--@llvm-project//libc:libc_math_mpfr` flag. It can take three values: - `external` (default) will build `mpfr` and `gmp` from source. - `system` will use the system installed `mpfr` library. - `disable` will skip tests relying on `mpfr`. Reviewed By: sivachandra, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D119547
2022-11-18 10:14:37 +00:00
)
load("@rules_foreign_cc//foreign_cc:repositories.bzl", "rules_foreign_cc_dependencies")
[bazel] Restore libpfm as a conditional dependency for exegesis. We used to have `pfm` built into exegesis, although since it's an external dependency we marked it as a manual target. Because of this we didn't have buildbot coverage and so we removed it in D134510 after we had a few breakages that weren't caught. This adds it back, but with three possible states similar to the story with `mpfr`, i.e. it can either be disabled, built from external sources (git/make), or use whatever `-lpfm` is installed on the system. This change is modeled after D119547. Like that patch, the default is off (matching the status quo), but unlike that patch we don't enable it for CI because IIRC we don't have the package installed there, and building from source might be expensive. We could enable it later either after installing it on buildbot machines or by measuring build cost and deeming it OK. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D138470
2022-12-28 08:13:20 -08:00
[reland][libc][bazel] Add tests to the bazel build This patch adds bazel tests for llvm-libc. Some math tests rely on the `mpfr` library. This is controlled via the `--@llvm-project//libc:libc_math_mpfr` flag. It can take three values: - `external` (default) will build `mpfr` and `gmp` from source. - `system` will use the system installed `mpfr` library. - `disable` will skip tests relying on `mpfr`. Reviewed By: sivachandra, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D119547
2022-11-18 10:14:37 +00:00
rules_foreign_cc_dependencies()
maybe(
http_archive,
name = "gmp",
build_file = "@llvm-raw//utils/bazel/third_party_build:gmp.BUILD",
sha256 = "fd4829912cddd12f84181c3451cc752be224643e87fac497b69edddadc49b4f2",
strip_prefix = "gmp-6.2.1",
urls = [
"https://gmplib.org/download/gmp/gmp-6.2.1.tar.xz",
"https://ftp.gnu.org/gnu/gmp/gmp-6.2.1.tar.xz",
],
)
[libc][test][NFC] bump mpfr version to 4.1.1
2022-11-21 09:38:42 +00:00
# https://www.mpfr.org/mpfr-current/
[bazel] Update the mpfr URL to a stable one mpfr has released a new version, and now the old tar.gz URL does not work anymore. Update the URL to a stable one.
2023-01-09 10:26:25 +01:00
#
# When updating to a newer version, don't use URLs with "mpfr-current" in them.
# Instead, find a stable URL like the one used currently.
[reland][libc][bazel] Add tests to the bazel build This patch adds bazel tests for llvm-libc. Some math tests rely on the `mpfr` library. This is controlled via the `--@llvm-project//libc:libc_math_mpfr` flag. It can take three values: - `external` (default) will build `mpfr` and `gmp` from source. - `system` will use the system installed `mpfr` library. - `disable` will skip tests relying on `mpfr`. Reviewed By: sivachandra, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D119547
2022-11-18 10:14:37 +00:00
maybe(
http_archive,
name = "mpfr",
build_file = "@llvm-raw//utils/bazel/third_party_build:mpfr.BUILD",
[libc][test][NFC] bump mpfr version to 4.1.1
2022-11-21 09:38:42 +00:00
sha256 = "9cbed5d0af0d9ed5e9f8dd013e17838eb15e1db9a6ae0d371d55d35f93a782a7",
strip_prefix = "mpfr-4.1.1",
[bazel] Update the mpfr URL to a stable one mpfr has released a new version, and now the old tar.gz URL does not work anymore. Update the URL to a stable one.
2023-01-09 10:26:25 +01:00
urls = ["https://www.mpfr.org/mpfr-4.1.1/mpfr-4.1.1.tar.gz"],
[reland][libc][bazel] Add tests to the bazel build This patch adds bazel tests for llvm-libc. Some math tests rely on the `mpfr` library. This is controlled via the `--@llvm-project//libc:libc_math_mpfr` flag. It can take three values: - `external` (default) will build `mpfr` and `gmp` from source. - `system` will use the system installed `mpfr` library. - `disable` will skip tests relying on `mpfr`. Reviewed By: sivachandra, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D119547
2022-11-18 10:14:37 +00:00
)
[libc][bazel] Add BUILD targets for complex functions and tests. (#129618) This involved a little bit of yak shaving because one of the new tests depends on MPC, and we didn't have targets for it yet, so I ended up needing to add a similar setup to what we have for MPFR.
2025-03-04 11:05:01 -08:00
maybe(
http_archive,
name = "mpc",
build_file = "@llvm-raw//utils/bazel/third_party_build:mpc.BUILD",
sha256 = "ab642492f5cf882b74aa0cb730cd410a81edcdbec895183ce930e706c1c759b8",
strip_prefix = "mpc-1.3.1",
urls = ["https://ftp.gnu.org/gnu/mpc/mpc-1.3.1.tar.gz"],
)
[bazel] Restore libpfm as a conditional dependency for exegesis. We used to have `pfm` built into exegesis, although since it's an external dependency we marked it as a manual target. Because of this we didn't have buildbot coverage and so we removed it in D134510 after we had a few breakages that weren't caught. This adds it back, but with three possible states similar to the story with `mpfr`, i.e. it can either be disabled, built from external sources (git/make), or use whatever `-lpfm` is installed on the system. This change is modeled after D119547. Like that patch, the default is off (matching the status quo), but unlike that patch we don't enable it for CI because IIRC we don't have the package installed there, and building from source might be expensive. We could enable it later either after installing it on buildbot machines or by measuring build cost and deeming it OK. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D138470
2022-12-28 08:13:20 -08:00
maybe(
[bazel] Replace git_repository with http_archive. (#99422) The current git_repository usage points to tags, which leads to warnings that the build may not be reproducable due to not using a git sha. The docs for [git_repository](https://bazel.build/rules/lib/repo/git#git_repository) recommend using `http_archive`, so switch to that instead. Also bump to newer versions for these two repos.
2024-07-18 21:56:37 -05:00
http_archive,
[bazel] Restore libpfm as a conditional dependency for exegesis. We used to have `pfm` built into exegesis, although since it's an external dependency we marked it as a manual target. Because of this we didn't have buildbot coverage and so we removed it in D134510 after we had a few breakages that weren't caught. This adds it back, but with three possible states similar to the story with `mpfr`, i.e. it can either be disabled, built from external sources (git/make), or use whatever `-lpfm` is installed on the system. This change is modeled after D119547. Like that patch, the default is off (matching the status quo), but unlike that patch we don't enable it for CI because IIRC we don't have the package installed there, and building from source might be expensive. We could enable it later either after installing it on buildbot machines or by measuring build cost and deeming it OK. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D138470
2022-12-28 08:13:20 -08:00
name = "pfm",
build_file = "@llvm-raw//utils/bazel/third_party_build:pfm.BUILD",
[bazel] Replace git_repository with http_archive. (#99422) The current git_repository usage points to tags, which leads to warnings that the build may not be reproducable due to not using a git sha. The docs for [git_repository](https://bazel.build/rules/lib/repo/git#git_repository) recommend using `http_archive`, so switch to that instead. Also bump to newer versions for these two repos.
2024-07-18 21:56:37 -05:00
sha256 = "d18b97764c755528c1051d376e33545d0eb60c6ebf85680436813fa5b04cc3d1",
strip_prefix = "libpfm-4.13.0",
urls = ["https://versaweb.dl.sourceforge.net/project/perfmon2/libpfm4/libpfm-4.13.0.tar.gz"],
[bazel] Restore libpfm as a conditional dependency for exegesis. We used to have `pfm` built into exegesis, although since it's an external dependency we marked it as a manual target. Because of this we didn't have buildbot coverage and so we removed it in D134510 after we had a few breakages that weren't caught. This adds it back, but with three possible states similar to the story with `mpfr`, i.e. it can either be disabled, built from external sources (git/make), or use whatever `-lpfm` is installed on the system. This change is modeled after D119547. Like that patch, the default is off (matching the status quo), but unlike that patch we don't enable it for CI because IIRC we don't have the package installed there, and building from source might be expensive. We could enable it later either after installing it on buildbot machines or by measuring build cost and deeming it OK. Reviewed By: GMNGeoffrey Differential Revision: https://reviews.llvm.org/D138470
2022-12-28 08:13:20 -08:00
)
[bazel] Port zstd support Originally added in D128465. Used by `llvm:Support` and `lld:ELF`. Enabled by default. Disable with `--@llvm_zstd//:llvm_enable_zstd=false`. Reviewed By: MaskRay, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D143344
2023-03-29 01:29:05 +02:00
maybe(
http_archive,
name = "llvm_zstd",
build_file = "@llvm-raw//utils/bazel/third_party_build:zstd.BUILD",
sha256 = "7c42d56fac126929a6a85dbc73ff1db2411d04f104fae9bdea51305663a83fd0",
strip_prefix = "zstd-1.5.2",
urls = [
[NFC] Reformat bzl files with buildifier
2024-02-12 11:35:17 -08:00
"https://github.com/facebook/zstd/releases/download/v1.5.2/zstd-1.5.2.tar.gz",
[bazel] Port zstd support Originally added in D128465. Used by `llvm:Support` and `lld:ELF`. Enabled by default. Disable with `--@llvm_zstd//:llvm_enable_zstd=false`. Reviewed By: MaskRay, GMNGeoffrey Differential Revision: https://reviews.llvm.org/D143344
2023-03-29 01:29:05 +02:00
],
)
[bazel] Add support for pybind (#98398) Previously these targets were disabled, but with a relatively new rules_python we can build these pointing at a hermetic python, which allows us to build these safely. Users can still access the files directly if they need to customize how these are built.
2024-07-18 17:23:02 -07:00
maybe(
http_archive,
name = "pybind11",
build_file = "@llvm-raw//utils/bazel/third_party_build:pybind.BUILD",
sha256 = "201966a61dc826f1b1879a24a3317a1ec9214a918c8eb035be2f30c3e9cfbdcb",
strip_prefix = "pybind11-2.10.3",
url = "https://github.com/pybind/pybind11/archive/v2.10.3.zip",
)
Revert "Revert "[mlir python] Add nanobind support (#119232) Reverts revert #118517 after (hopefully) fixing builders (https://github.com/llvm/llvm-zorg/pull/328, https://github.com/llvm/llvm-zorg/pull/327) This reverts commit 61bf308cf2fc32452f14861c102ace89f5f36fec.
2024-12-09 16:37:43 -05:00
maybe(
http_archive,
name = "robin_map",
build_file = "@llvm-raw//utils/bazel/third_party_build:robin_map.BUILD",
[bazel] Add rules for clang-fuzzer protobuf-related libraries (#123126) Also bumped up bazel_skylib to the latest version because the proto rules were complaining about a missing feature.
2025-01-16 10:12:46 -08:00
sha256 = "a8424ad3b0affd4c57ed26f0f3d8a29604f0e1f2ef2089f497f614b1c94c7236",
strip_prefix = "robin-map-1.3.0",
Revert "Revert "[mlir python] Add nanobind support (#119232) Reverts revert #118517 after (hopefully) fixing builders (https://github.com/llvm/llvm-zorg/pull/328, https://github.com/llvm/llvm-zorg/pull/327) This reverts commit 61bf308cf2fc32452f14861c102ace89f5f36fec.
2024-12-09 16:37:43 -05:00
url = "https://github.com/Tessil/robin-map/archive/refs/tags/v1.3.0.tar.gz",
)
maybe(
http_archive,
name = "nanobind",
build_file = "@llvm-raw//utils/bazel/third_party_build:nanobind.BUILD",
[mlir python] Port Python core code to nanobind. (#120473) Relands #118583, with a fix for Python 3.8 compatibility. It was not possible to set the buffer protocol accessers via slots in Python 3.8. Why? https://nanobind.readthedocs.io/en/latest/why.html says it better than I can, but my primary motivation for this change is to improve MLIR IR construction time from JAX. For a complicated Google-internal LLM model in JAX, this change improves the MLIR lowering time by around 5s (out of around 30s), which is a significant speedup for simply switching binding frameworks. To a large extent, this is a mechanical change, for instance changing `pybind11::` to `nanobind::`. Notes: * this PR needs Nanobind 2.4.0, because it needs a bug fix (https://github.com/wjakob/nanobind/pull/806) that landed in that release. * this PR does not port the in-tree dialect extension modules. They can be ported in a future PR. * I removed the py::sibling() annotations from def_static and def_class in `PybindAdapters.h`. These ask pybind11 to try to form an overload with an existing method, but it's not possible to form mixed pybind11/nanobind overloads this ways and the parent class is now defined in nanobind. Better solutions may be possible here. * nanobind does not contain an exact equivalent of pybind11's buffer protocol support. It was not hard to add a nanobind implementation of a similar API. * nanobind is pickier about casting to std::vector<bool>, expecting that the input is a sequence of bool types, not truthy values. In a couple of places I added code to support truthy values during casting. * nanobind distinguishes bytes (`nb::bytes`) from strings (e.g., `std::string`). This required nb::bytes overloads in a few places.
2024-12-18 21:55:42 -05:00
sha256 = "bb35deaed7efac5029ed1e33880a415638352f757d49207a8e6013fefb6c49a7",
strip_prefix = "nanobind-2.4.0",
url = "https://github.com/wjakob/nanobind/archive/refs/tags/v2.4.0.tar.gz",
Revert "Revert "[mlir python] Add nanobind support (#119232) Reverts revert #118517 after (hopefully) fixing builders (https://github.com/llvm/llvm-zorg/pull/328, https://github.com/llvm/llvm-zorg/pull/327) This reverts commit 61bf308cf2fc32452f14861c102ace89f5f36fec.
2024-12-09 16:37:43 -05:00
)
[bazel] Add support for pybind (#98398) Previously these targets were disabled, but with a relatively new rules_python we can build these pointing at a hermetic python, which allows us to build these safely. Users can still access the files directly if they need to customize how these are built.
2024-07-18 17:23:02 -07:00
load("@rules_python//python:repositories.bzl", "py_repositories", "python_register_toolchains")
py_repositories()
python_register_toolchains(
name = "python_3_12",
python_version = "3.12",
)
Reference in New Issue Copy Permalink