| commit | 5e9e52cb2f75fc748f630f7344ccb78139fd1153 | [log] [tgz] |
|---|---|---|
| author | Aaron Green <aarongreen@pigweed.infra.roller.google.com> | Tue Sep 24 20:17:40 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 24 20:17:40 2024 +0000 |
| tree | 2b0de87ad2b51ccf044727076275958b04c799b0 | |
| parent | dc2d99a3b4e1ae3b628e7a7d084132ef0d53a449 [diff] |
roll: third_party/pigweed pw_allocator: Store TestHarness::Allocation inline This module include a TestHarness class which can generate requests for an allocator to allocate, reallocate and deallocate regions of memory. Previously, this harness took a vector of Allocation structs that was used to stored the details of these requests. This allowed, for example, the test harness to deallocate memory that had previously been allocated. Requiring this vector could result in significant overhead if a substantial number of allocations were to be tested at once. This overhead is unecessary though, as there is another place to store the request details: in the allocations themselves! This change sets a minimum size and alignment on requests. It makes the Allocation struct an IntrusiveList item, and stores the Allocations in the allocated memory. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/230894 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Original-Revision: a4dab0be18a649c79759880308ed051b0a2576a4 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: e81f65b16a544f..a4dab0be18a649 Roller-URL: https://ci.chromium.org/b/8735884578674069025 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Idba0a86ab161a96f24af90a336b1ce819bf356e6 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/237638 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
This repository outlines the recommended way of using Pigweed in a new or existing project. Feel free to fork this repository, or read it as a reference.
For more information see the Pigweed Getting started guide.
Check back for more complex examples and features coming soon!
Make sure you've set up Pigweed's prerequisites.
If you're on Windows, you can automate the initial setup by downloading the first-time setup script from cmd.exe:
curl https://pigweed.googlesource.com/pigweed/sample_project/+/main/tools/setup_windows_prerequisites.bat?format=TEXT > setup_pigweed_prerequisites.b64 && certutil -decode -f setup_pigweed_prerequisites.b64 setup_pigweed_prerequisites.bat && del setup_pigweed_prerequisites.b64
Then you can run the script with the following command in cmd.exe:
setup_pigweed_prerequisites.bat
Note: You may see a few UAC prompts as the script installs Git, Python, and enables developer mode.
Once that is done, you can clone this project with the following command:
git clone https://pigweed.googlesource.com/pigweed/sample_project
Pigweed uses a local development environment for most of its tools. This means tools are not installed to your machine, and are instead stored in a directory inside your project (Note: git ignores this directory). The tools are temporarily added to the PATH of the current shell session.
To make sure the latest tooling has been fetched and set up, run the bootstrap command for your operating system:
Windows
bootstrap.bat
Linux & Mac
source ./bootstrap.sh
After tooling updates, you might need to run bootstrap again to ensure the latest tools.
After the initial bootstrap, you can use use the activate scripts to configure the current shell for development without doing a full update.
Windows
activate.bat
Linux & Mac
source ./activate.sh
All of these commands must be run from inside an activated developer environment. See Environment setup
To build the project, documentation, and tests, run the following command in an activated environment:
pw build
Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:
pw watch
When you pull latest repository changes, run bootstrap:
source ./bootstrap.sh
If you're just launching a new shell session, you can activate instead:
source ./activate.sh
and rebuild with:
pw build
Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.