-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Always use -Wl,--warn-unresolved-symbols
in MSAN builds
#48835
Conversation
I'm not sure I understand. |
I think MSAN builds (somewhat) work only on x86_64 linux. @gbaraldi is that correct? |
MSAN only exists on linux currently so yeah. |
Ok, according to the docs builds with sanitizer might work also on macOS. I change it to add % make SANITIZE=1 SANITIZE_MEMORY=1 print-SANITIZE_LDFLAGS
SANITIZE_LDFLAGS= -fsanitize=memory -fsanitize-memory-track-origins -fno-omit-frame-pointer which looks good. |
Sanitizers work on macos fine. Specifically ASAN and TSAN, but MSAN is Linux and some BSDs only. At least currently. But that looks fine. |
* Always use `-Wl,--warn-unresolved-symbols` in MSAN builds * Use `-Wl,--warn-unresolved-symbols` only on Linux and FreeBSD (cherry picked from commit a07f512)
* Always use `-Wl,--warn-unresolved-symbols` in MSAN builds * Use `-Wl,--warn-unresolved-symbols` only on Linux and FreeBSD (cherry picked from commit a07f512)
One of the two ways I could think of to fix #48732. The other one is to use
-Wl,--warn-unresolved-symbols
in suitesparse only when doing the MSAN build, but I figured that this flag might be useful for other packages as well.CC: @fxcoudert.