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

Thread sanitizer UI test fails on Macos ARM64 #88131

Closed
hkratz opened this issue Aug 18, 2021 · 3 comments
Closed

Thread sanitizer UI test fails on Macos ARM64 #88131

hkratz opened this issue Aug 18, 2021 · 3 comments
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state O-macos Operating system: macOS

Comments

@hkratz
Copy link
Contributor

hkratz commented Aug 18, 2021

Try on a Apple Silicon Mac:

./configure --build=aarch64-apple-darwin --enable-sanitizers --enable-profiler --set rust.jemalloc --set llvm.ninja=false
./x.py test --stage 1  src/test/ui/sanitize/thread.rs

Expected result: Test passes.

Actual result: Test fails with:

running 1 test
test [ui] ui/sanitize/thread.rs ... FAILED

failures:

---- [ui] ui/sanitize/thread.rs stdout ----

error: error pattern ' WARNING: ThreadSanitizer: data race' not found!

error: error pattern ' Location is heap block of size 4' not found!

error: error pattern ' allocated by main thread' not found!

error: multiple error patterns not found
status: signal: 6
command: "..."
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
ThreadSanitizer: unsupported vm address limit 0x800000000000, expected 0x000fc0000000.

------------------------------------------

@rustbot label +A-sanitizer +A-llvm +O-macos +O-arm

@hkratz hkratz added the C-bug Category: This is a bug. label Aug 18, 2021
@rustbot rustbot added A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state O-macos Operating system: macOS labels Aug 18, 2021
@hkratz
Copy link
Contributor Author

hkratz commented Aug 18, 2021

Was probably already fixed upstream, see https://reviews.llvm.org/rG8a8fa09cb78af47ad81e933045fc20ddce8482ff. Not sure what the situation for LLVM 13 is.

@hkratz
Copy link
Contributor Author

hkratz commented Aug 18, 2021

I can confirm that this is fixed in LLVM 13, it passes for me locally with #87570.

@hkratz
Copy link
Contributor Author

hkratz commented Aug 21, 2021

Fixed with the LLVM 13 merge.

@hkratz hkratz closed this as completed Aug 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. C-bug Category: This is a bug. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state O-macos Operating system: macOS
Projects
None yet
Development

No branches or pull requests

2 participants