mirror of
https://pdfium.googlesource.com/pdfium
synced 2026-08-02 05:04:39 +08:00
6be4f3be70
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>
28 lines
829 B
Plaintext
28 lines
829 B
Plaintext
# Copyright 2024 The PDFium Authors. All rights reserved.
|
|
# Use of this source code is governed by a BSD-style license that can be
|
|
# found in the LICENSE file.
|
|
|
|
# The set of path prefixes that should be checked for unsafe buffer usage (see
|
|
# -Wunsafe-buffer-usage in Clang).
|
|
#
|
|
# ***
|
|
# Paths should be written as relative to the root of the source tree with
|
|
# unix-style path separators. Directory prefixes should end with `/`, such
|
|
# as `base/`.
|
|
# ***
|
|
#
|
|
# Files in this set are known to not use pointer arithmetic/subscripting, and
|
|
# make use of constructs like base::span or containers like std::vector instead.
|
|
#
|
|
# See `docs/unsafe_buffers.md`.
|
|
|
|
# These directories are excluded because they come from outside PDFium and
|
|
# we don't have control over their contents.
|
|
-base/
|
|
-samples/
|
|
-skia/
|
|
-testing/
|
|
-third_party/
|
|
-tools/
|
|
-v8/
|