github-repos/benchmark
1
0
Fork 0
mirror of https://github.com/google/benchmark.git synced 2025-03-15 11:40:12 +08:00
Code Issues Packages Projects Releases Wiki Activity
5a4c459548
benchmark/WORKSPACE

21 lines
430 B
Python
Raw Normal View History

Add support for building with Bazel. (#533) * Add myself to CONTRIBUTORS under the corp CLA for Stripe, Inc. * Add support for building with Bazel. Limitations compared to existing CMake rules: * Defaults to using C++11 `<regex>`, with an override via Bazel flag `--define` of `google_benchmark.have_regex`. The TravisCI config sets the regex implementation to `posix` because it uses ancient compilers. * Debug vs Opt mode can't be set per test. TravisCI runs all the tests in debug mode to satisfy `diagnostics_test`, which depends on `CHECK` being live. * Set Bazel workspace name so other repos can refer to it by stable name. This is recommended by the Bazel style guide to avoid each dependent workspace defining its own name for the dependency.
2018-03-08 20:48:46 +08:00
workspace(name = "com_github_google_benchmark")
Add a `benchmark_deps.bzl` function to Google Benchmark (#1520) * Add `benchmark_workspace.bzl` function This commit adds a `benchmark_workspace.bzl` function to Google Benchmark. It is intended to be used as a means to pull in Google Benchmark's build dependencies in its own Bazel workspace, as well as in workspaces of downstream projects. * Migrate WORKSPACE to use the newly created benchmark_deps.bzl This commit changes Google Benchmark's own WORKSPACE to use the newly created `benchmark_deps.bzl` function.
2022-12-19 19:12:32 +08:00
load("//:bazel/benchmark_deps.bzl", "benchmark_deps")
Load http_archive for bazel build
2019-04-09 20:02:45 +08:00
Add a `benchmark_deps.bzl` function to Google Benchmark (#1520) * Add `benchmark_workspace.bzl` function This commit adds a `benchmark_workspace.bzl` function to Google Benchmark. It is intended to be used as a means to pull in Google Benchmark's build dependencies in its own Bazel workspace, as well as in workspaces of downstream projects. * Migrate WORKSPACE to use the newly created benchmark_deps.bzl This commit changes Google Benchmark's own WORKSPACE to use the newly created `benchmark_deps.bzl` function.
2022-12-19 19:12:32 +08:00
benchmark_deps()
[bazel] Build libpfm as a dependency to allow collection of perf counters (#1408) * Build libpfm as a dependency to allow collection of perf counters This commit builds libpfm using rules_foreign_cc and lets the default build of the benchmark library support perf counter collection without needing additional work from users. Tested with a custom target: ``` bazel run \ --override_repository=com_github_google_benchmark=/home/raghu/benchmark \ -c opt :test-bench -- "--benchmark_perf_counters=INSTRUCTIONS,CYCLES" Using profile: local <snip> ---------------------------------------------------------------------- Benchmark Time CPU Iterations UserCounters... ---------------------------------------------------------------------- BM_Test 0.279 ns 0.279 ns 1000000000 CYCLES=1.00888 INSTRUCTIONS=2 ``` Signed-off-by: Raghu Raja <raghu@enfabrica.net> * Adding myself to the CONTRIBUTORS file per CLA guidance Enfabrica has already signed a corporate CLA. Signed-off-by: Raghu Raja <raghu@enfabrica.net> Signed-off-by: Raghu Raja <raghu@enfabrica.net>
2022-10-31 19:03:59 +08:00
Upgrade core bazel dependencies (#1711) Bumps `rules_foreign_cc` to v0.10.1 (October 2023), `bazel_skylib` to v1.5.0 (November 2023), `rules_python` to v0.27.1 (December 2023). Also syncs GoogleTest to v1.12.1 (the last C++11 supporting version) to be the same as in MODULE.bazel. Since the latest `rules_python` changed its setup calling convention, that is updated also in the WORKSPACE file.
2023-12-07 23:00:43 +08:00
load("@rules_python//python:repositories.bzl", "py_repositories")
[bazel] Build libpfm as a dependency to allow collection of perf counters (#1408) * Build libpfm as a dependency to allow collection of perf counters This commit builds libpfm using rules_foreign_cc and lets the default build of the benchmark library support perf counter collection without needing additional work from users. Tested with a custom target: ``` bazel run \ --override_repository=com_github_google_benchmark=/home/raghu/benchmark \ -c opt :test-bench -- "--benchmark_perf_counters=INSTRUCTIONS,CYCLES" Using profile: local <snip> ---------------------------------------------------------------------- Benchmark Time CPU Iterations UserCounters... ---------------------------------------------------------------------- BM_Test 0.279 ns 0.279 ns 1000000000 CYCLES=1.00888 INSTRUCTIONS=2 ``` Signed-off-by: Raghu Raja <raghu@enfabrica.net> * Adding myself to the CONTRIBUTORS file per CLA guidance Enfabrica has already signed a corporate CLA. Signed-off-by: Raghu Raja <raghu@enfabrica.net> Signed-off-by: Raghu Raja <raghu@enfabrica.net>
2022-10-31 19:03:59 +08:00
Upgrade core bazel dependencies (#1711) Bumps `rules_foreign_cc` to v0.10.1 (October 2023), `bazel_skylib` to v1.5.0 (November 2023), `rules_python` to v0.27.1 (December 2023). Also syncs GoogleTest to v1.12.1 (the last C++11 supporting version) to be the same as in MODULE.bazel. Since the latest `rules_python` changed its setup calling convention, that is updated also in the WORKSPACE file.
2023-12-07 23:00:43 +08:00
py_repositories()
load("@rules_python//python:pip.bzl", "pip_parse")
pip_parse(
Add pre-commit config and GitHub Actions job (#1688) * Add pre-commit config and GitHub Actions job Contains the following hooks: * buildifier - for formatting and linting Bazel files. * mypy, ruff, isort, black - for Python typechecking, import hygiene, static analysis, and formatting. The pylint CI job was changed to be a pre-commit CI job, where pre-commit is bootstrapped via Python. Pylint is currently no longer part of the code checks, but can be re-added if requested. The reason to drop was that it does not play nicely with pre-commit, and lots of its functionality and responsibilities are actually covered in ruff. * Add dev extra to pyproject.toml for development installs * Clarify that pre-commit contains only Python and Bazel hooks * Add one-line docstrings to Bazel modules * Apply buildifier pre-commit fixes to Bazel files * Apply pre-commit fixes to Python files * Supply --profile=black to isort to prevent conflicts * Fix nanobind build file formatting * Add tooling configs to `pyproject.toml` In particular, set line length 80 for all Python files. * Reformat all Python files to line length 80, fix return type annotations Also ignores the `tools/compare.py` and `tools/gbench/report.py` files for mypy, since they emit a barrage of errors which we can deal with later. The errors are mostly related to dynamic classmethod definition.
2023-10-30 23:35:37 +08:00
name = "tools_pip_deps",
Upgrade core bazel dependencies (#1711) Bumps `rules_foreign_cc` to v0.10.1 (October 2023), `bazel_skylib` to v1.5.0 (November 2023), `rules_python` to v0.27.1 (December 2023). Also syncs GoogleTest to v1.12.1 (the last C++11 supporting version) to be the same as in MODULE.bazel. Since the latest `rules_python` changed its setup calling convention, that is updated also in the WORKSPACE file.
2023-12-07 23:00:43 +08:00
requirements_lock = "//tools:requirements.txt",
Add Python bindings. (#957) * Add Python bindings. * Add license headers. * Change example to a test. * Add example usage to module docstring.
2020-05-07 00:28:29 +08:00
)
Upgrade core bazel dependencies (#1711) Bumps `rules_foreign_cc` to v0.10.1 (October 2023), `bazel_skylib` to v1.5.0 (November 2023), `rules_python` to v0.27.1 (December 2023). Also syncs GoogleTest to v1.12.1 (the last C++11 supporting version) to be the same as in MODULE.bazel. Since the latest `rules_python` changed its setup calling convention, that is updated also in the WORKSPACE file.
2023-12-07 23:00:43 +08:00
load("@tools_pip_deps//:requirements.bzl", "install_deps")
install_deps()
Reference in New Issue Copy Permalink