Rename pdfium_unsafe_buffers_paths.txt file
In preparation for a day in which the dependent product source trees
are searched for these unsafe suppression files, make the naming
consistent between chrome and pdfium.
Bug: 389830173
Change-Id: I0b4eba50015791c3fb34040401e42ae27b3b38e7
Reviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/127891
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Thomas Sepez <tsepez@google.com>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
diff --git a/.gn b/.gn
index fac25bb..6a6bbb0 100644
--- a/.gn
+++ b/.gn
@@ -26,7 +26,7 @@
v8_imminent_deprecation_warnings = false
# PDFium has its own unsafe-buffers enforcement directories.
- clang_unsafe_buffers_paths = "//pdfium_unsafe_buffers_paths.txt"
+ clang_unsafe_buffers_paths = "//unsafe_buffers_paths.txt"
}
no_check_targets = [
diff --git a/pdfium_unsafe_buffers_paths.txt b/unsafe_buffers_paths.txt
similarity index 100%
rename from pdfium_unsafe_buffers_paths.txt
rename to unsafe_buffers_paths.txt
