-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Sanitizers target modificators #138736
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
base: master
Are you sure you want to change the base?
Sanitizers target modificators #138736
Conversation
This comment has been minimized.
This comment has been minimized.
7526d38
to
0777169
Compare
This comment has been minimized.
This comment has been minimized.
0777169
to
f454b02
Compare
This comment has been minimized.
This comment has been minimized.
f454b02
to
509e0b3
Compare
This comment has been minimized.
This comment has been minimized.
509e0b3
to
1f20a51
Compare
This comment has been minimized.
This comment has been minimized.
1f20a51
to
fc95e77
Compare
This comment has been minimized.
This comment has been minimized.
e025a55
to
c54dcfc
Compare
☔ The latest upstream changes (presumably #138974) made this pull request unmergeable. Please resolve the merge conflicts. |
r? compiler |
Do we have any tests that check simultaneous use of multiple sanitizers? For example, if I enable both shadow-call-stack and kcfi at the same time, then both must also be enabled in deps. |
@rustbot claim |
Looks like flaky network failure. @bors try jobs=dist-i686-linux |
This comment has been minimized.
This comment has been minimized.
…s, r=<try> Sanitizers target modificators try-job: dist-i686-linux
@bors retry (flaky) |
…s, r=rcvalle Sanitizers target modificators Depends on bool flag fix: #138483. Some sanitizers need to be target modifiers, and some do not. For now, we should mark all sanitizers as target modifiers except for these: AddressSanitizer, LeakSanitizer For kCFI, the helper flag -Zsanitizer-cfi-normalize-integers should also be a target modifier. Many test errors was with sanizer flags inconsistent with std deps. Tests are fixed with `-C unsafe-allow-abi-mismatch`.
A job failed! Check out the build log: (web) (plain enhanced) (plain) Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Network failure (#t-infra > Non-stop network timeouts across auto-builds) @bors retry |
Giving this rollup=never PR a boost while I deal with the last rollup failure. @bors p=1 |
…s, r=rcvalle Sanitizers target modificators Depends on bool flag fix: #138483. Some sanitizers need to be target modifiers, and some do not. For now, we should mark all sanitizers as target modifiers except for these: AddressSanitizer, LeakSanitizer For kCFI, the helper flag -Zsanitizer-cfi-normalize-integers should also be a target modifier. Many test errors was with sanizer flags inconsistent with std deps. Tests are fixed with `-C unsafe-allow-abi-mismatch`.
💔 Test failed - checks-actions |
@bors p=0 |
Not sure if this actually failed, or CI is just being weird again. @bors try jobs=aarch64-apple |
This comment has been minimized.
This comment has been minimized.
…s, r=<try> Sanitizers target modificators try-job: aarch64-apple
@bors retry |
Depends on bool flag fix: #138483.
Some sanitizers need to be target modifiers, and some do not. For now, we should mark all sanitizers as target modifiers except for these: AddressSanitizer, LeakSanitizer
For kCFI, the helper flag -Zsanitizer-cfi-normalize-integers should also be a target modifier.
Many test errors was with sanizer flags inconsistent with std deps. Tests are fixed with
-C unsafe-allow-abi-mismatch
.