Skip to content

rustc should print an unambiguous error message when building no_std binaries with panic=unwind #45533

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

Closed
Trolldemorted opened this issue Oct 25, 2017 · 1 comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@Trolldemorted
Copy link
Contributor

As we have found out in #45492, rustc cannot (yet) build a no_std binary when compiling with panic=unwind.

Instead of aborting and printing an error message, rustc builds objects that have external dependencies, in msvc's case __CxxFrameHandler3.

@TimNN TimNN added A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one. labels Oct 31, 2017
@Mark-Simulacrum
Copy link
Member

Today we say "error: #[panic_handler] function required, but not found" which seems basically perfect since that'll lead you to https://doc.rust-lang.org/nomicon/panic-handler.html which'll hopefully make it mostly clear what needs to happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Development

No branches or pull requests

3 participants