Google Git
Sign in
pigweed/pigweed/quickstart/bazel/e1893a59a9fcd9322b8325024df42d34fe7b9729
commit
e1893a59a9fcd9322b8325024df42d34fe7b9729
[log]
author
Austin Foxley <afoxley@pigweed.infra.roller.google.com>
Mon Jun 29 11:22:31 2026 -0700
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Mon Jun 29 11:22:31 2026 -0700
tree
76ee60a8834640cd9156522b89d931fcf35c0365
parent
ec673265ee31c6127a656592fcda96c0980f1519 [diff]
roll: pigweed pw_containers: Optimize GenericDeque inserts

Since GenericDeque underlying storage is not contiguous, inserting items
is not able to be optimized into a memcpy for trivially copyable types.
If we split the range into the two contiguous chunks, the compiler
can use memcpy instead of copying item by item.

Example speed up for ValueType==std::byte is 30x faster on an insert of
1000 items.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/429412
Original-Revision: d6b65080e9037ff7957d8d0bbb860316445b72b8

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: c9ff6d3eed2b31..d6b65080e9037f
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8677637508388240129
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Iefd6a28c193d1a19d351a0dae136c53e82f862f1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/430494
1 file changed
tree: 76ee60a8834640cd9156522b89d931fcf35c0365
  1. .github/
  2. .vscode/
  3. apps/
  4. modules/
  5. system/
  6. targets/
  7. tools/
  8. .bazelignore
  9. .bazelrc
  10. .bazelversion
  11. .buildifier.json
  12. .clang-format
  13. .clang-tidy
  14. .clangd.shared
  15. .gitignore
  16. .pw_console.yaml
  17. .pylintrc
  18. AUTHORS
  19. BUILD.bazel
  20. CONTRIBUTING.md
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. mypy.ini
  25. OWNERS
  26. pw
  27. README.md
  28. workflows.json
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It is a LED-blinking service (featuring RPC control!) for the Raspberry Pi Pico. It can also be run on any computer using the included simulator.

Getting the code

git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart
cd pw_bazel_quickstart

Dependencies

The only dependency that must be installed is Bazelisk.

Bazelisk is a launcher for the Bazel build system that allows for easy management of multiple Bazel versions.

Instructions for installing Bazelisk can be found here.

Running on the simulator

To run the simulator, type: bazelisk run //apps/blinky:simulator_blinky Then, in a new console, connect to the simulator using: bazelisk run //apps/blinky:simulator_console

Running on hardware

To start, connect a Raspberry Pi Pico, Pico 2, or debug probe via USB.

To run on the Raspberry Pi Pico, type: bazelisk run //apps/blinky:flash_rp2040 Then, in a new console, connect to the device using: bazelisk run //apps/blinky:rp2040_console

Controlling the LED

Once connected with a console, RPCs can be sent to control the LED. Try running:

device.set_led(True)
device.set_led(False)
device.toggle_led()
device.blink(blink_count=3)

Running unit tests on the host device

bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.

Running unit tests on hardware

bazelisk run @pigweed//targets/rp2040/py:unit_test_server in one console followed by bazelisk test //... --config=rp2040 will also allow running the unit tests on-device.

Next steps

Try poking around the codebase for inspiration about how Pigweed projects can be organized. Most of the relevant code in this quickstart (including RPC definitions) is inside modules/blinky, with some client-side Python code in tools/console.py.