-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: New sanitizers config #469
Conversation
3f08ab0
to
10dacc0
Compare
10dacc0
to
e023d2c
Compare
a74cbbc
to
5bb8a96
Compare
159eeea
to
9575c60
Compare
Codecov Report
@@ Coverage Diff @@
## master #469 +/- ##
=======================================
Coverage 98.23% 98.23%
=======================================
Files 62 62
Lines 9023 9024 +1
=======================================
+ Hits 8864 8865 +1
Misses 159 159 |
e191da5
to
4ecd2a1
Compare
4730eb7
to
d2d6241
Compare
The "pointer-subtract" sanitizer is disabled because GCC fails to compile constexpr function with pointer subtraction. The bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97145 is to be fixed in GCC 10.3.
This reverts commit 5e1bd16.
This requires to lower the call depth limit to |
What potential issues would gcc find over clang? Can we do this limit conditionally when building for sanitizer-gcc target? |
I don't know really. They seem to have similar features, but have different bugs and versions of asan. E.g. I can enable
Please, no. I don't want to build and test different versions of Fizzy depending on debug options, sanitizer configuration, etc. |
512 as a call depth seems a bit on the slim side though. |
No description provided.