head 1.4; access; symbols netbsd-11-0-RC4:1.3 netbsd-11-0-RC3:1.3 netbsd-11-0-RC2:1.3 netbsd-11-0-RC1:1.3 gcc-14-3-0:1.1.1.3 perseant-exfatfs-base-20250801:1.3 netbsd-11:1.3.0.4 netbsd-11-base:1.3 gcc-12-5-0:1.1.1.2 perseant-exfatfs-base-20240630:1.3 gcc-12-4-0:1.1.1.2 perseant-exfatfs:1.3.0.2 perseant-exfatfs-base:1.3 gcc-12-3-0:1.1.1.2 gcc-10-5-0:1.1.1.1 gcc-10-4-0:1.1.1.1 cjep_sun2x:1.2.0.4 cjep_sun2x-base:1.2 cjep_staticlib_x-base1:1.2 cjep_staticlib_x:1.2.0.2 cjep_staticlib_x-base:1.2 gcc-10-3-0:1.1.1.1 FSF:1.1.1; locks; strict; comment @// @; 1.4 date 2025.09.14.00.08.56; author mrg; state Exp; branches; next 1.3; commitid x9D5QEnvbeMI4CaG; 1.3 date 2023.07.31.01.44.56; author mrg; state Exp; branches; next 1.2; commitid q79F5Opf0FLsyTyE; 1.2 date 2021.04.11.23.54.27; author mrg; state dead; branches; next 1.1; commitid wJn7ggfUTEMOWVOC; 1.1 date 2021.04.10.22.09.22; author mrg; state Exp; branches 1.1.1.1; next ; commitid eC4g0MRpqTvEkNOC; 1.1.1.1 date 2021.04.10.22.09.22; author mrg; state Exp; branches; next 1.1.1.2; commitid eC4g0MRpqTvEkNOC; 1.1.1.2 date 2023.07.30.05.20.40; author mrg; state Exp; branches; next 1.1.1.3; commitid tk6nV4mbc9nVEMyE; 1.1.1.3 date 2025.09.13.23.45.04; author mrg; state Exp; branches; next ; commitid KwhwN4krNWa6XBaG; desc @@ 1.4 log @merge GCC 14.3.0. @ text @//===-- sanitizer_coverage_fuchsia.cpp ------------------------------------===// // // Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions. // See https://llvm.org/LICENSE.txt for license information. // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception // //===----------------------------------------------------------------------===// // // Sanitizer Coverage Controller for Trace PC Guard, Fuchsia-specific version. // // This Fuchsia-specific implementation uses the same basic scheme and the // same simple '.sancov' file format as the generic implementation. The // difference is that we just produce a single blob of output for the whole // program, not a separate one per DSO. We do not sort the PC table and do // not prune the zeros, so the resulting file is always as large as it // would be to report 100% coverage. Implicit tracing information about // the address ranges of DSOs allows offline tools to split the one big // blob into separate files that the 'sancov' tool can understand. // // Unlike the traditional implementation that uses an atexit hook to write // out data files at the end, the results on Fuchsia do not go into a file // per se. The 'coverage_dir' option is ignored. Instead, they are stored // directly into a shared memory object (a Zircon VMO). At exit, that VMO // is handed over to a system service that's responsible for getting the // data out to somewhere that it can be fed into the sancov tool (where and // how is not our problem). #include "sanitizer_platform.h" #if SANITIZER_FUCHSIA #include #include #include #include "sanitizer_atomic.h" #include "sanitizer_common.h" #include "sanitizer_interface_internal.h" #include "sanitizer_internal_defs.h" #include "sanitizer_symbolizer_fuchsia.h" using namespace __sanitizer; namespace __sancov { namespace { // TODO(mcgrathr): Move the constant into a header shared with other impls. constexpr u64 Magic64 = 0xC0BFFFFFFFFFFF64ULL; static_assert(SANITIZER_WORDSIZE == 64, "Fuchsia is always LP64"); constexpr const char kSancovSinkName[] = "sancov"; // Collects trace-pc guard coverage. // This class relies on zero-initialization. class TracePcGuardController final { public: constexpr TracePcGuardController() {} // For each PC location being tracked, there is a u32 reserved in global // data called the "guard". At startup, we assign each guard slot a // unique index into the big results array. Later during runtime, the // first call to TracePcGuard (below) will store the corresponding PC at // that index in the array. (Each later call with the same guard slot is // presumed to be from the same PC.) Then it clears the guard slot back // to zero, which tells the compiler not to bother calling in again. At // the end of the run, we have a big array where each element is either // zero or is a tracked PC location that was hit in the trace. // This is called from global constructors. Each translation unit has a // contiguous array of guard slots, and a constructor that calls here // with the bounds of its array. Those constructors are allowed to call // here more than once for the same array. Usually all of these // constructors run in the initial thread, but it's possible that a // dlopen call on a secondary thread will run constructors that get here. void InitTracePcGuard(u32 *start, u32 *end) { if (end > start && *start == 0 && common_flags()->coverage) { // Complete the setup before filling in any guards with indices. // This avoids the possibility of code called from Setup reentering // TracePcGuard. u32 idx = Setup(end - start); for (u32 *p = start; p < end; ++p) { *p = idx++; } } } void TracePcGuard(u32 *guard, uptr pc) { atomic_uint32_t *guard_ptr = reinterpret_cast(guard); u32 idx = atomic_exchange(guard_ptr, 0, memory_order_relaxed); if (idx > 0) array_[idx] = pc; } void Dump() { Lock locked(&setup_lock_); if (array_) { CHECK_NE(vmo_, ZX_HANDLE_INVALID); // Publish the VMO to the system, where it can be collected and // analyzed after this process exits. This always consumes the VMO // handle. Any failure is just logged and not indicated to us. __sanitizer_publish_data(kSancovSinkName, vmo_); vmo_ = ZX_HANDLE_INVALID; // This will route to __sanitizer_log_write, which will ensure that // information about shared libraries is written out. This message // uses the `dumpfile` symbolizer markup element to highlight the // dump. See the explanation for this in: // https://fuchsia.googlesource.com/zircon/+/master/docs/symbolizer_markup.md Printf("SanitizerCoverage: " FORMAT_DUMPFILE " with up to %u PCs\n", kSancovSinkName, vmo_name_, next_index_ - 1); } } private: // We map in the largest possible view into the VMO: one word // for every possible 32-bit index value. This avoids the need // to change the mapping when increasing the size of the VMO. // We can always spare the 32G of address space. static constexpr size_t MappingSize = sizeof(uptr) << 32; Mutex setup_lock_; uptr *array_ = nullptr; u32 next_index_ = 0; zx_handle_t vmo_ = {}; char vmo_name_[ZX_MAX_NAME_LEN] = {}; size_t DataSize() const { return next_index_ * sizeof(uintptr_t); } u32 Setup(u32 num_guards) { Lock locked(&setup_lock_); DCHECK(common_flags()->coverage); if (next_index_ == 0) { CHECK_EQ(vmo_, ZX_HANDLE_INVALID); CHECK_EQ(array_, nullptr); // The first sample goes at [1] to reserve [0] for the magic number. next_index_ = 1 + num_guards; zx_status_t status = _zx_vmo_create(DataSize(), ZX_VMO_RESIZABLE, &vmo_); CHECK_EQ(status, ZX_OK); // Give the VMO a name including our process KOID so it's easy to spot. internal_snprintf(vmo_name_, sizeof(vmo_name_), "%s.%zu", kSancovSinkName, internal_getpid()); _zx_object_set_property(vmo_, ZX_PROP_NAME, vmo_name_, internal_strlen(vmo_name_)); uint64_t size = DataSize(); status = _zx_object_set_property(vmo_, ZX_PROP_VMO_CONTENT_SIZE, &size, sizeof(size)); CHECK_EQ(status, ZX_OK); // Map the largest possible view we might need into the VMO. Later // we might need to increase the VMO's size before we can use larger // indices, but we'll never move the mapping address so we don't have // any multi-thread synchronization issues with that. uintptr_t mapping; status = _zx_vmar_map(_zx_vmar_root_self(), ZX_VM_PERM_READ | ZX_VM_PERM_WRITE, 0, vmo_, 0, MappingSize, &mapping); CHECK_EQ(status, ZX_OK); // Hereafter other threads are free to start storing into // elements [1, next_index_) of the big array. array_ = reinterpret_cast(mapping); // Store the magic number. // Hereafter, the VMO serves as the contents of the '.sancov' file. array_[0] = Magic64; return 1; } else { // The VMO is already mapped in, but it's not big enough to use the // new indices. So increase the size to cover the new maximum index. CHECK_NE(vmo_, ZX_HANDLE_INVALID); CHECK_NE(array_, nullptr); uint32_t first_index = next_index_; next_index_ += num_guards; zx_status_t status = _zx_vmo_set_size(vmo_, DataSize()); CHECK_EQ(status, ZX_OK); uint64_t size = DataSize(); status = _zx_object_set_property(vmo_, ZX_PROP_VMO_CONTENT_SIZE, &size, sizeof(size)); CHECK_EQ(status, ZX_OK); return first_index; } } }; static TracePcGuardController pc_guard_controller; } // namespace } // namespace __sancov namespace __sanitizer { void InitializeCoverage(bool enabled, const char *dir) { CHECK_EQ(enabled, common_flags()->coverage); CHECK_EQ(dir, common_flags()->coverage_dir); static bool coverage_enabled = false; if (!coverage_enabled) { coverage_enabled = enabled; Atexit(__sanitizer_cov_dump); AddDieCallback(__sanitizer_cov_dump); } } } // namespace __sanitizer extern "C" { SANITIZER_INTERFACE_ATTRIBUTE void __sanitizer_dump_coverage(const uptr *pcs, uptr len) { UNIMPLEMENTED(); } SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_pc_guard, u32 *guard) { if (!*guard) return; __sancov::pc_guard_controller.TracePcGuard(guard, GET_CALLER_PC() - 1); } SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_pc_guard_init, u32 *start, u32 *end) { if (start == end || *start) return; __sancov::pc_guard_controller.InitTracePcGuard(start, end); } SANITIZER_INTERFACE_ATTRIBUTE void __sanitizer_dump_trace_pc_guard_coverage() { __sancov::pc_guard_controller.Dump(); } SANITIZER_INTERFACE_ATTRIBUTE void __sanitizer_cov_dump() { __sanitizer_dump_trace_pc_guard_coverage(); } // Default empty implementations (weak). Users should redefine them. SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_cmp, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_cmp1, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_cmp2, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_cmp4, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_cmp8, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_const_cmp1, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_const_cmp2, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_const_cmp4, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_const_cmp8, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_switch, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_div4, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_div8, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_gep, void) {} SANITIZER_INTERFACE_WEAK_DEF(void, __sanitizer_cov_trace_pc_indir, void) {} } // extern "C" #endif // !SANITIZER_FUCHSIA @ 1.3 log @make this actually be GCC 12.3.0's libsanitizer. the libsanitizer we used with GCC 9 and GCC 10 was significantly ahead of the GCC 9 and GCC 10 provided versions. @ text @d36 1 @ 1.2 log @revert sanitizer back to the version we were using with GCC 9, since that one was already newer than the GCC 10 version. @ text @d30 4 a38 4 #include #include #include d54 2 d87 2 a88 1 if (idx > 0) array_[idx] = pc; d92 1 a92 1 BlockingMutexLock locked(&setup_lock_); d119 1 a119 1 BlockingMutex setup_lock_ = BlockingMutex(LINKER_INITIALIZED); d128 1 a128 1 BlockingMutexLock locked(&setup_lock_); d146 4 d182 4 d218 2 a219 1 if (!*guard) return; d225 2 a226 1 if (start == end || *start) return; @ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @initial import of GCC 10.3.0. main changes include: caveats: - ABI issue between c++14 and c++17 fixed - profile mode is removed from libstdc++ - -fno-common is now the default new features: - new flags -fallocation-dce, -fprofile-partial-training, -fprofile-reproducible, -fprofile-prefix-path, and -fanalyzer - many new compile and link time optimisations - enhanced drive optimisations - openacc 2.6 support - openmp 5.0 features - new warnings: -Wstring-compare and -Wzero-length-bounds - extended warnings: -Warray-bounds, -Wformat-overflow, -Wrestrict, -Wreturn-local-addr, -Wstringop-overflow, -Warith-conversion, -Wmismatched-tags, and -Wredundant-tags - some likely C2X features implemented - more C++20 implemented - many new arm & intel CPUs known hundreds of reported bugs are fixed. full list of changes can be found at: https://gcc.gnu.org/gcc-10/changes.html @ text @@ 1.1.1.2 log @initial import of GCC 12.3.0. major changes in GCC 11 included: - The default mode for C++ is now -std=gnu++17 instead of -std=gnu++14. - When building GCC itself, the host compiler must now support C++11, rather than C++98. - Some short options of the gcov tool have been renamed: -i to -j and -j to -H. - ThreadSanitizer improvements. - Introduce Hardware-assisted AddressSanitizer support. - For targets that produce DWARF debugging information GCC now defaults to DWARF version 5. This can produce up to 25% more compact debug information compared to earlier versions. - Many optimisations. - The existing malloc attribute has been extended so that it can be used to identify allocator/deallocator API pairs. A pair of new -Wmismatched-dealloc and -Wmismatched-new-delete warnings are added. - Other new warnings: -Wsizeof-array-div, enabled by -Wall, warns about divisions of two sizeof operators when the first one is applied to an array and the divisor does not equal the size of the array element. -Wstringop-overread, enabled by default, warns about calls to string functions reading past the end of the arrays passed to them as arguments. -Wtsan, enabled by default, warns about unsupported features in ThreadSanitizer (currently std::atomic_thread_fence). - Enchanced warnings: -Wfree-nonheap-object detects many more instances of calls to deallocation functions with pointers not returned from a dynamic memory allocation function. -Wmaybe-uninitialized diagnoses passing pointers or references to uninitialized memory to functions taking const-qualified arguments. -Wuninitialized detects reads from uninitialized dynamically allocated memory. -Warray-parameter warns about functions with inconsistent array forms. -Wvla-parameter warns about functions with inconsistent VLA forms. - Several new features from the upcoming C2X revision of the ISO C standard are supported with -std=c2x and -std=gnu2x. - Several C++20 features have been implemented. - The C++ front end has experimental support for some of the upcoming C++23 draft. - Several new C++ warnings. - Enhanced Arm, AArch64, x86, and RISC-V CPU support. - The implementation of how program state is tracked within -fanalyzer has been completely rewritten with many enhancements. see https://gcc.gnu.org/gcc-11/changes.html for a full list. major changes in GCC 12 include: - An ABI incompatibility between C and C++ when passing or returning by value certain aggregates containing zero width bit-fields has been discovered on various targets. x86-64, ARM and AArch64 will always ignore them (so there is a C ABI incompatibility between GCC 11 and earlier with GCC 12 or later), PowerPC64 ELFv2 always take them into account (so there is a C++ ABI incompatibility, GCC 4.4 and earlier compatible with GCC 12 or later, incompatible with GCC 4.5 through GCC 11). RISC-V has changed the handling of these already starting with GCC 10. As the ABI requires, MIPS takes them into account handling function return values so there is a C++ ABI incompatibility with GCC 4.5 through 11. - STABS: Support for emitting the STABS debugging format is deprecated and will be removed in the next release. All ports now default to emit DWARF (version 2 or later) debugging info or are obsoleted. - Vectorization is enabled at -O2 which is now equivalent to the original -O2 -ftree-vectorize -fvect-cost-model=very-cheap. - GCC now supports the ShadowCallStack sanitizer. - Support for __builtin_shufflevector compatible with the clang language extension was added. - Support for attribute unavailable was added. - Support for __builtin_dynamic_object_size compatible with the clang language extension was added. - New warnings: -Wbidi-chars warns about potentially misleading UTF-8 bidirectional control characters. -Warray-compare warns about comparisons between two operands of array type. - Some new features from the upcoming C2X revision of the ISO C standard are supported with -std=c2x and -std=gnu2x. - Several C++23 features have been implemented. - Many C++ enhancements across warnings and -f options. see https://gcc.gnu.org/gcc-12/changes.html for a full list. @ text @a29 4 #include #include #include d35 4 a53 2 constexpr TracePcGuardController() {} d85 1 a85 2 if (idx > 0) array_[idx] = pc; d89 1 a89 1 Lock locked(&setup_lock_); d116 1 a116 1 Mutex setup_lock_; d125 1 a125 1 Lock locked(&setup_lock_); a142 4 uint64_t size = DataSize(); status = _zx_object_set_property(vmo_, ZX_PROP_VMO_CONTENT_SIZE, &size, sizeof(size)); CHECK_EQ(status, ZX_OK); a174 4 uint64_t size = DataSize(); status = _zx_object_set_property(vmo_, ZX_PROP_VMO_CONTENT_SIZE, &size, sizeof(size)); CHECK_EQ(status, ZX_OK); d207 1 a207 2 if (!*guard) return; d213 1 a213 2 if (start == end || *start) return; @ 1.1.1.3 log @initial import of GCC 14.3.0. major changes in GCC 13: - improved sanitizer - zstd debug info compression - LTO improvements - SARIF based diagnostic support - new warnings: -Wxor-used-as-pow, -Wenum-int-mismatch, -Wself-move, -Wdangling-reference - many new -Wanalyzer* specific warnings - enhanced warnings: -Wpessimizing-move, -Wredundant-move - new attributes to mark file descriptors, c++23 "assume" - several C23 features added - several C++23 features added - many new features for Arm, x86, RISC-V major changes in GCC 14: - more strict C99 or newer support - ia64* marked deprecated (but seemingly still in GCC 15.) - several new hardening features - support for "hardbool", which can have user supplied values of true/false - explicit support for stack scrubbing upon function exit - better auto-vectorisation support - added clang-compatible __has_feature and __has_extension - more C23, including -std=c23 - several C++26 features added - better diagnostics in C++ templates - new warnings: -Wnrvo, Welaborated-enum-base - many new features for Arm, x86, RISC-V - possible ABI breaking change for SPARC64 and small structures with arrays of floats. @ text @a35 1 #include "sanitizer_interface_internal.h" @