Skip to content
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

Closed
wants to merge 5 commits into from
Closed

ci: New sanitizers config #469

wants to merge 5 commits into from

Conversation

chfast
Copy link
Collaborator

@chfast chfast commented Aug 10, 2020

No description provided.

@chfast chfast force-pushed the gcc_sanitizers branch 3 times, most recently from 3f08ab0 to 10dacc0 Compare August 10, 2020 14:46
@chfast chfast changed the title ci: Add GCC sanitizers job ci: New sanitizers config Sep 22, 2020
@chfast chfast force-pushed the gcc_sanitizers branch 2 times, most recently from a74cbbc to 5bb8a96 Compare September 23, 2020 12:53
@chfast chfast force-pushed the gcc_sanitizers branch 3 times, most recently from 159eeea to 9575c60 Compare October 6, 2020 10:01
@chfast chfast marked this pull request as ready for review October 6, 2020 10:02
@chfast chfast requested review from gumb0 and axic October 6, 2020 10:02
@codecov
Copy link

codecov bot commented Oct 6, 2020

Codecov Report

Merging #469 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #469   +/-   ##
=======================================
  Coverage   98.23%   98.23%           
=======================================
  Files          62       62           
  Lines        9023     9024    +1     
=======================================
+ Hits         8864     8865    +1     
  Misses        159      159           

@chfast chfast force-pushed the gcc_sanitizers branch 2 times, most recently from e191da5 to 4ecd2a1 Compare October 6, 2020 12:05
@axic axic changed the base branch from master to call_depth October 6, 2020 16:40
@chfast chfast force-pushed the call_depth branch 2 times, most recently from 4730eb7 to d2d6241 Compare October 7, 2020 07:01
Base automatically changed from call_depth to master October 7, 2020 07:22
@chfast chfast marked this pull request as draft October 7, 2020 07:41
@chfast chfast changed the base branch from master to sanitizers_config October 7, 2020 07:56
Base automatically changed from sanitizers_config to master October 7, 2020 08:52
chfast added 3 commits October 7, 2020 11:17
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.
@chfast
Copy link
Collaborator Author

chfast commented Oct 7, 2020

This requires to lower the call depth limit to 512.

@chfast chfast closed this Oct 7, 2020
@axic axic mentioned this pull request Oct 7, 2020
@axic
Copy link
Member

axic commented Oct 9, 2020

What potential issues would gcc find over clang?

Can we do this limit conditionally when building for sanitizer-gcc target?

@chfast
Copy link
Collaborator Author

chfast commented Oct 9, 2020

What potential issues would gcc find over clang?

I don't know really. They seem to have similar features, but have different bugs and versions of asan. E.g. I can enable pointer-compare check in GCC while it is broken in Clang.

Can we do this limit conditionally when building for sanitizer-gcc target?

Please, no. I don't want to build and test different versions of Fizzy depending on debug options, sanitizer configuration, etc.

@axic
Copy link
Member

axic commented Oct 9, 2020

512 as a call depth seems a bit on the slim side though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants