-
Notifications
You must be signed in to change notification settings - Fork 10.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
[SR-9474] Swift 5.0 'Sanitizers' test failures on PowerPC64LE #51936
Comments
Does TSan work on PowerPC64LE with non-Swift code? |
Comment by Sarvesh Tamba (JIRA) Hi @belkadan, apologies, however I am quite new to Swift. 🙂 Is there a way to find if TSan work on PowerPC64LE with non-Swift code? |
TSan (Thread Sanitizer) is an LLVM/Clang feature that you can read about here: https://clang.llvm.org/docs/ThreadSanitizer.html. I wouldn't take that list of supported platforms too seriously, though; that doc looks pretty old. You'll have to look around to find out. |
Comment by Sarvesh Tamba (JIRA) Getting the following stack trace dump for both the Sanitizers test cases:
|
Comment by Sarvesh Tamba (JIRA) Hi @belkadan In the link mentioned by you, I checked link under section "More Information" - https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual Supported Platforms: I will disable this for PowerPC64LE and test further. |
Attachment: Download
Environment
PowerPC64LE(Little Endian) - Ubuntu 16.04.4 LTS
Additional Detail from JIRA
md5: 030568327a69a224a8b6083143ffc5ed
Issue Description:
The following Sanitizers test failures are seen when Swift 5.0 toolchain is built on PowerPC64LE.
Invoked the build-toolchain to run the tests as follows :-
utils/build-toolchain srtbundle --test
**Following are the Sanitizers test failures:-
Swift(linux-powerpc64le) :: Sanitizers/tsan.swift
Swift(linux-powerpc64le) :: Sanitizers/witness_table_lookup.swift
Are these tests valid for PowerPC64LE?
Attached are the error details of the failing tests.
SanitizersTestFailures.txt
The text was updated successfully, but these errors were encountered: