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

Cranelift backend for rustc #257

Closed
bjorn3 opened this issue Mar 12, 2020 · 3 comments · Fixed by #269
Closed

Cranelift backend for rustc #257

bjorn3 opened this issue Mar 12, 2020 · 3 comments · Fixed by #269

Comments

@bjorn3
Copy link
Member

bjorn3 commented Mar 12, 2020

Meeting proposal info

  • Title: Cranelift backend for rustc
  • Type: technical

Summary

The current LLVM backend for rustc is very good at optimizing functions. However it is not the fastest, even with optimizations disabled. When compiling in release mode this is not a big problem, but during development this can be annoying. Cranelift has the potential to improve compilation time, as it is optimized for compilation time as opposed to being optimized for good optimizations like LLVM. Over the course of the past ~1.5 year I have been working on a Cranelift based codegen backend for rustc (rustc_codegen_cranelift or cg_clif for short). It is currently complete enough to compile many programs. While there are cases where LLVM is faster, Cranelift is already faster than LLVM in many cases.

Rustc_codegen_cranelift is currently at a point where it may make sense to talk about bringing support in tree. This meeting proposal is about talking if we do want this and to talk about the future of rustc_codegen_cranelift in general.

More details and meeting outline in this hackmd

About this issue

This issue corresponds to a meeting proposal for the compiler team
steering meeting. It corresponds to a possible topic of
discussion. You can read more about the steering meeting procedure
here
.

Comment policy

These issues are meant to be used as an "announcements channel"
regarding the proposal, and not as a place to discuss the technical
details. Feel free to subscribe to updates. We'll post comments when
reviewing the proposal in meetings or making a scheduling decision.
In the meantime, if you have questions or ideas, ping the proposers
on Zulip (or elsewhere).

@bjorn3
Copy link
Member Author

bjorn3 commented Mar 13, 2020

More information can be found at https://hackmd.io/@bjorn3/HJL5ryFS8.

@RalfJung
Copy link
Member

The target feature detection x86 doesn’t work as inline assembly support is missing.

This is also a problem for Miri. Would be great to find a unified solution. :)

@bjorn3
Copy link
Member Author

bjorn3 commented Mar 13, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants