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

Add StatementKind::Intrinsic to MIR #348

Closed
3 tasks done
JulianKnodt opened this issue Aug 21, 2020 · 7 comments
Closed
3 tasks done

Add StatementKind::Intrinsic to MIR #348

JulianKnodt opened this issue Aug 21, 2020 · 7 comments
Labels
major-change A proposal to make a major change to rustc major-change-accepted A major change proposal that was accepted T-compiler Add this label so rfcbot knows to poll the compiler team

Comments

@JulianKnodt
Copy link

JulianKnodt commented Aug 21, 2020

Proposal

Extend Mir to include statements for specific intrinsic function calls that are known to not panic or unwind under any conditions. Currently, function calls can only be used in terminator position, but permitting intrinsics which have better known behaviour to be interspersed will make it easier to create optimizations in the future.

Create a specialized terminator for the optimization of certain intrinsics. Specifically, proposing StatementKind::CopyNonOverlapping since memcpy is a function we often want to optimize over. The structure of the statement for this intrinsic would be StatementKind::CopyNonOverlapping { src: Box<Place<'tcx>>, dst: Box<Place<'tcx>>, size: Operand }. This would be easy enough to convert in the future to a nested StatementKind::Intrinsic operator if more additions are added.

Mentors or Reviewers

@oli-obk

Process

The main points of the Major Change Process is as follows:

  • File an issue describing the proposal.
  • A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
    • Finding a "second" suffices for internal changes. If however you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
    • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
  • Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

@JulianKnodt JulianKnodt added T-compiler Add this label so rfcbot knows to poll the compiler team major-change A proposal to make a major change to rustc labels Aug 21, 2020
@rustbot
Copy link
Collaborator

rustbot commented Aug 21, 2020

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

@rustbot rustbot added the to-announce Announce this issue on triage meeting label Aug 21, 2020
@JulianKnodt JulianKnodt changed the title Add StatementKind::Call to MIR [MCP] Add StatementKind::Call to MIR Aug 21, 2020
@JulianKnodt JulianKnodt changed the title [MCP] Add StatementKind::Call to MIR Add StatementKind::Call to MIR Aug 21, 2020
@JulianKnodt
Copy link
Author

Also see:
rust-lang/rust#39685 (comment)

@spastorino spastorino removed the to-announce Announce this issue on triage meeting label Aug 26, 2020
@JulianKnodt JulianKnodt changed the title Add StatementKind::Call to MIR Add StatementKind::Intrinsic to MIR Sep 7, 2020
@eddyb
Copy link
Member

eddyb commented Sep 10, 2020

Extend Mir to include statements for specific intrinsic function calls that are known under any circumstance to panic or unwind.

Is this missing a negation?

@JulianKnodt
Copy link
Author

ah yes, yes it is

@nikomatsakis
Copy link
Contributor

@rustbot second

@rustbot rustbot added the final-comment-period The FCP has started, most (if not all) team members are in agreement label Sep 18, 2020
@nagisa
Copy link
Member

nagisa commented Sep 18, 2020

@rustbot third

I’m willing to review changes that implement this too, so do r? me on implementation PRs as well.

@spastorino spastorino added major-change-accepted A major change proposal that was accepted and removed final-comment-period The FCP has started, most (if not all) team members are in agreement labels Sep 30, 2020
@rustbot rustbot added the to-announce Announce this issue on triage meeting label Sep 30, 2020
@spastorino spastorino removed the to-announce Announce this issue on triage meeting label Oct 1, 2020
@RalfJung
Copy link
Member

RalfJung commented Oct 4, 2020

Extend Mir to include statements for specific intrinsic function calls that are known to not panic or unwind under any conditions.

Additionally, these intrinsics must also be known to always return (i.e., they must never cause an infinite loop).

m-ou-se added a commit to m-ou-se/rust that referenced this issue Mar 9, 2021
Add StatementKind::CopyNonOverlapping

Implements rust-lang/compiler-team#348

r? `@nagisa`
JohnTitor added a commit to JohnTitor/rust that referenced this issue Mar 9, 2021
Add StatementKind::CopyNonOverlapping

Implements rust-lang/compiler-team#348

r? `@nagisa`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major-change A proposal to make a major change to rustc major-change-accepted A major change proposal that was accepted T-compiler Add this label so rfcbot knows to poll the compiler team
Projects
None yet
Development

No branches or pull requests

7 participants