[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-bugs
Subject:    [Bug sanitizer/97229] pointer-compare sanitizer is very slow due to __asan::IsAddressNearGlobal
From:       mail at milianw dot de via Gcc-bugs <gcc-bugs () gcc ! gnu ! org>
Date:       2020-09-30 13:26:13
Message-ID: bug-97229-4-EDFQ6dQEIH () http ! gcc ! gnu ! org/bugzilla/
[Download RAW message or body]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97229

--- Comment #2 from Milian Wolff <mail at milianw dot de> ---
As I said, >99% of the samples point to this backtrace:

```
<our code>
__sanitizer_ptr_cmp
__asanCheckForInvalidPointerPair
__asanCheckForInvalidPointerPair
__asan::IsInvalidPointerPair
__asan::GetGlobalAddressInformation(unsigned long, unsigned long, ...)
__asan::GetGlobalsForAddress(unsigned long, __asan_global*, ...)
__asan::isAddressNearGlobal
```

if you want per-line cost attribution, I'd first have to compile the sanitizer
runtime with debug symbols.

If you really need the `perf report` output instead (why?) I can redo the
measurement again.=
[prev in list] [next in list] [prev in thread] [next in thread]