commit | 76efa10a575f2bc4ebbb0348f97daf79e7d1532c | [log] [tgz] |
---|---|---|
author | Thomas Lukaszewicz <tluk@chromium.org> | Thu Mar 06 20:26:11 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 06 20:26:11 2025 |
tree | 8b7705e38bf99e48151c57a13ee312422dae5605 | |
parent | a03787ae167a53eeb6c0e834ff82b64f1ef55588 [diff] |
[code cache] Update //tools/code_cache_generator to take multiple files This CL updates code_cache_generator to take the following command-line params: - in_files: comma-separated list of files - in_folder: folder path under which in_files exist - out_folder: folder path for the generated code cache files - out_file_suffix: the suffix appended to in_files This update allows generation of code cache output files for multiple in_files for a single instantiation of the associated v8 environment. This change does not change the expected input or outputs of the generate_code_cache webui build utility, which is asserted under the webui_resources_tools_python_unittests test suite (see generate_code_cache_test.py) Bug: 378504039 Change-Id: I3ac720ca05c56a6b150d54d72a48eff184e6f3b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6332394 Reviewed-by: Fred Shih <ffred@chromium.org> Commit-Queue: Tom Lukaszewicz <tluk@chromium.org> Cr-Commit-Position: refs/heads/main@{#1429095}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.