-
Notifications
You must be signed in to change notification settings - Fork 13.3k
SIGSEGV during benchmark but build succeeds #94793
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
Comments
Extracted bitcode still crashes llc on LLVM trunk. |
Okay, this is less interesting than I thought. Reduced test case:
Asserts with:
The problem being that SDNodes only support up to 2^16 values, and we're performing a load with more than many constituent parts. It looks like there are already a few upstream reports for this issue: llvm/llvm-project#53164 and llvm/llvm-project#40691 As the issue is exotic, I don't expect this to gain much traction. |
Nice finds! Strange that it only causes the SIGSEGV on |
I'll tentatively assign a P-low based on @nikic comment, discussion is on Zulip thread of the Prioritization Working Group, can be re-evaluated if necessary. @rustbot label -I-prioritize +P-low |
FYI I encountered this as well: #136282 |
I've fallen victim to the Wordle bug and started writing a thing to analyse winning games for initial guesses and such. After getting to a certain point I decided to try benchmarking parts of it, and wrote a little file to do so. Then when I ran
cargo criterion
, I ended up getting:or something similar. Note the
signal: 11, SIGSEGV: invalid memory reference
way off to the right - just wanna bring attention to it since it's a pretty darn wide message. Anywho. I also attempted to run a stacktrace of it ingdb
, which didn't yield a whole lot. The whole log when run with the core dump is:Also weird is the sheer amount of time it takes to produce that. Even from a clean build,
cargo build --release
takes only some 8-10 seconds (and succeeds, unlikecargo criterion
), but from an incremental build with all the dependencies already compiled,cargo criterion
takes 5-7 minutes.Meta
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: