[Bug sanitizer/97416] New: pointer-compare sanitizer + use-after-return: CHECK failed: /build/gcc/src/gcc/libsanitizer/asan/asan_thread.cpp:369 "((bottom)) != (0)" (0x0, 0x0)

2020-10-14 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97416 Bug ID: 97416 Summary: pointer-compare sanitizer + use-after-return: CHECK failed: /build/gcc/src/gcc/libsanitizer/asan/asan_thread.cpp:3 69 "((bottom)) != (0)"

[Bug sanitizer/97229] pointer-compare sanitizer is very slow due to __asan::IsAddressNearGlobal

2020-09-30 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97229 --- Comment #2 from Milian Wolff --- As I said, >99% of the samples point to this backtrace: ``` __sanitizer_ptr_cmp __asanCheckForInvalidPointerPair __asanCheckForInvalidPointerPair __asan::IsInvalidPointerPair

[Bug sanitizer/97229] New: pointer-compare sanitizer is very slow due to __asan::IsAddressNearGlobal

2020-09-28 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97229 Bug ID: 97229 Summary: pointer-compare sanitizer is very slow due to __asan::IsAddressNearGlobal Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity:

[Bug analyzer/100705] New: warn about dead store

2021-05-20 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100705 Bug ID: 100705 Summary: warn about dead store Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer

[Bug sanitizer/100878] New: enabling UBSAN leads to false positive `'this' pointer is null` when casting lambda to function pointer

2021-06-02 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100878 Bug ID: 100878 Summary: enabling UBSAN leads to false positive `'this' pointer is null` when casting lambda to function pointer Product: gcc Version: 11.1.0 Status:

[Bug c++/99386] New: std::variant overhead much larger compared to clang

2021-03-04 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99386 Bug ID: 99386 Summary: std::variant overhead much larger compared to clang Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug c++/99386] std::variant overhead much larger compared to clang

2021-03-04 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99386 --- Comment #2 from Milian Wolff --- in both cases libstdc++ is being used: ``` gcc: linux-vdso.so.1 (0x7ffdc9f93000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x7f1449b2d000) libm.so.6 => /usr/lib/libm.so.6

[Bug c++/99386] std::variant overhead much larger compared to clang

2021-03-04 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99386 --- Comment #3 from Milian Wolff --- Ah, seems like `-O2 -flto` fixes the issue for me, but how come clang can pull this off without LTO?

[Bug c++/99386] std::variant overhead much larger compared to clang

2021-03-04 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99386 --- Comment #4 from Milian Wolff --- Ah, but LTO only helps with the variant that contains a single type. The variant with two types remains very slow: variant with single type: ``` Performance counter stats for './variant 1' (5 runs):

[Bug sanitizer/102984] strange alignment issues with std::vector::emplace/push_back and overaligned type

2021-10-28 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102984 --- Comment #2 from Milian Wolff --- Similarly: std::vector locks(10); // works std::vector locks(10, spinlock()); // doesn't work This report here was motivated by stumbling over this report over at

[Bug sanitizer/102984] New: strange alignment issues with std::vector::emplace/push_back and overaligned type

2021-10-28 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102984 Bug ID: 102984 Summary: strange alignment issues with std::vector::emplace/push_back and overaligned type Product: gcc Version: 11.1.0 Status: UNCONFIRMED

[Bug c++/103131] -Wpedantic doesn't warn about extra semicolons anymore

2021-11-08 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103131 --- Comment #1 from Milian Wolff --- correction: gcc version 10 and below used to complain

[Bug c++/103131] New: -Wpedantic doesn't warn about extra semicolons anymore

2021-11-08 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103131 Bug ID: 103131 Summary: -Wpedantic doesn't warn about extra semicolons anymore Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug libstdc++/102984] strange alignment issues with std::vector::emplace/push_back and overaligned type

2021-10-29 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102984 Milian Wolff changed: What|Removed |Added Resolution|--- |FIXED Status|WAITING

[Bug sanitizer/100878] enabling UBSAN leads to false positive `'this' pointer is null` when casting lambda to function pointer

2021-07-21 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100878 Milian Wolff changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Known to fail|

[Bug sanitizer/101576] New: -fsaniitize=undefined silences clear nullptr dereference warning at compile time

2021-07-22 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101576 Bug ID: 101576 Summary: -fsaniitize=undefined silences clear nullptr dereference warning at compile time Product: gcc Version: 11.1.0 Status: UNCONFIRMED

[Bug tree-optimization/80635] [10 regression] std::optional and bogus -Wmaybe-uninitialized warning

2022-11-16 Thread mail at milianw dot de via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635 Milian Wolff changed: What|Removed |Added CC||mail at milianw dot de --- Comment #69