Skip to content

stdio related segfault (ARM regression affecting 1.9+) #33181

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.

Sign up for GitHub

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

Jump to bottom
Closed
MagaTailor opened this issue Apr 24, 2016 · 4 comments
Closed

stdio related segfault (ARM regression affecting 1.9+) #33181

MagaTailor opened this issue Apr 24, 2016 · 4 comments
Labels
O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state

Comments

@MagaTailor
Copy link

Issue #32359 doesn't reproduce in 1.8 stable and it doesn't trigger when redirecting console output to a file.

If the issue is actually related to LLVM in any way (via parallel codegen), the relevant difference could be clang, as rustc 1.8 used here, had been built with it.
@MagaTailor
Copy link
Author

Confirmed with rustc 1.9.0-beta.1 (37a2869af 2016-04-12) from the same source which means clang is not a factor.

@MagaTailor MagaTailor changed the title stdio related ARM regression affecting 1.9+ stdio related segfault (ARM regression affecting 1.9+) Apr 25, 2016
@MagaTailor
Copy link
Author

MagaTailor commented May 8, 2016 •
edited
Loading

It seems the default opt-level=3 used by this project was to blame in part. Neither 2, nor z produce the crashing binary.

@eddyb Did something happen between rust 1.8 and 1.9, either in the bundled LLVM or rustc that would affect the highest level of optimisations? (using parallel codegen)

cc @michaelwoerister

@MagaTailor MagaTailor mentioned this issue May 8, 2016
Closed
@MagaTailor
Copy link
Author

@eddyb I've just tried the obvious (after last night's patch) and MIR doesn't produce crashing code!

Old trans still does though...

@steveklabnik steveklabnik added the O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state label Jul 25, 2016
@MagaTailor MagaTailor mentioned this issue Jul 31, 2016
Closed
@MagaTailor
Copy link
Author

@eddyb Is there any use keeping this open? MIR trans is unaffected and I'm not going to try to reproduce it again.

@eddyb eddyb closed this as completed Jul 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@steveklabnik @eddyb @MagaTailor