
#pragma allow_unsafe_buffers
to all.
When I enabled by '-WUnsafe-buffer-usage` by default in every directories, I left behind several sub-directories. This patch adds the exceptions, allowing a subsequent patch to update `build/config/unsafe_buffers_paths.txt` to include these directories. Note: This still excludes: - Third party code. - Submodules: v8, clang, ... - Directories that were initially excluded because I couldn't get a config for them: //ios, //chromecast, ... - Others. See the N-1 patchset for the list of considered directories. See internal doc about it: https://docs.google.com/document/d/1erdcokeh6rfBqs_h0drHqSLtbDbB61j7j3O2Pz8NH78/edit?resourcekey=0-hNe6w1hYAYyVXGEpWI7HVA&tab=t.0 Cq-Include-Trybots: luci.chrome.try:win-chrome Cq-Include-Trybots: luci.chrome.try:win64-chrome Cq-Include-Trybots: luci.chromium.try:android-arm64-rel Cq-Include-Trybots: luci.chromium.try:android-cronet-arm64-rel Cq-Include-Trybots: luci.chromium.try:chromeos-arm-generic-rel Cq-Include-Trybots: luci.chromium.try:chromeos-libfuzzer-asan-rel Cq-Include-Trybots: luci.chromium.try:linux-asan-rel Cq-Include-Trybots: luci.chromium.try:linux-cast-arm-rel Cq-Include-Trybots: luci.chromium.try:linux-libfuzzer-asan-rel Cq-Include-Trybots: luci.chromium.try:win-libfuzzer-asan-rel Bug: 40285824 Change-Id: I52ba1c514f5e093d64b161af8ec2d91d0d988140 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6067126 Commit-Queue: Daniel Cheng <dcheng@chromium.org> Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Owners-Override: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1399018}
Chromium
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.