gecko-dev/build/sanitizers/ubsan_suppressions.txt

# This list contains runtime suppression entries for any issues reported
# by UndefinedBehaviorSanitizer (UBSan). Unlike the compile-time blacklists,
# this list allows us to blacklist source code files and functions only for
# specific checks performed by UBSan.
#
# Example:
#
# signed-integer-overflow:file-with-known-overflow.cpp
# alignment:function_doing_unaligned_access
# vptr:shared_object_with_vptr_failures.so
#
# Since runtime suppressions are much more expensive than compile-time
# blacklisting, this list should not be used for frequent issues but rather
# only for sporadic warnings that have already been checked and confirmed
# to not be bugs.
Bug 1373256 - Changes to support -fsanitize=integer in the codebase. r=froydnj The -fsanitize=integer analysis from UBSan can be helpful to detect signed and unsigned integer overflows in the codebase. Unfortunately, those occur very frequently, making it impossible to test anything with it without the use of a huge blacklist. This patch includes a blacklist that is broad enough to silence everything that would drain performance too much. But even with this blacklist, neither tests nor fuzzing is "clean". We can however in the future combine this with static analysis to limit ourselves to interesting places to look at, or improve the dynamic analysis to omit typical benign overflows. It also adds another attribute that can be used on functions. It is not used right now because it was initially easier to add things to the compile-time blacklist to get started. Finally, it includes a runtime suppression list and patches various parts in the test harnesses to support that. It is currently empty and it should not be used on frequent overflows because it is expensive. However, it has the advantage that it can be used to differentiate between signed and unsigned overflows while the compile-time blacklist cannot do that. So it can be used to e.g. silence unsigned integer overflows on a file or function while still reporting signed issues. We can also use this suppression list for any other UBSan related suppressions, should we ever want to use other features from that sanitizer. MozReview-Commit-ID: C5ofhfJdpCS --HG-- extra : rebase_source : 952043a441b41b2f58ec4abc51ac15fa71fc142f 2017-04-09 13:59:26 +03:00			`# This list contains runtime suppression entries for any issues reported`
			`# by UndefinedBehaviorSanitizer (UBSan). Unlike the compile-time blacklists,`
			`# this list allows us to blacklist source code files and functions only for`
			`# specific checks performed by UBSan.`
			`#`
			`# Example:`
			`#`
			`# signed-integer-overflow:file-with-known-overflow.cpp`
			`# alignment:function_doing_unaligned_access`
			`# vptr:shared_object_with_vptr_failures.so`
			`#`
			`# Since runtime suppressions are much more expensive than compile-time`
			`# blacklisting, this list should not be used for frequent issues but rather`
			`# only for sporadic warnings that have already been checked and confirmed`
			`# to not be bugs.`