commit | 1a12e3f3ebccb4c4bbc6df3756408e5445a3629d | [log] [tgz] |
---|---|---|
author | twerth <twerth@google.com> | Fri Oct 16 06:50:38 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 16 06:52:04 2020 -0700 |
tree | 0dc47364354add3f8e7d6e2cac8e520ffc971975 | |
parent | 676d6301111d60f7e975fd7df36ea9883f610a19 [diff] |
bazel profiler: remove TaskStack data structure It is unnecessary to keep the stack around explicitly when we also can pass the data to the closure. Previously, the stack was also used to verify that the profiler calls are consistent / properly nested. This became unnecessary with unknown commit which also made `completeTask` private. Removing `taskStack` also removes the potential for race conditions when stopping the profiler. PiperOrigin-RevId: 337497234
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md