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.

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

Inline direct calls to transmute in the frontend #15396

Closed
pcwalton opened this issue Jul 4, 2014 · 2 comments
Closed

Inline direct calls to transmute in the frontend #15396

pcwalton opened this issue Jul 4, 2014 · 2 comments
Labels
A-codegen Area: Code generation I-compiletime Issue: Problems and improvements with respect to compile times. I-slow Issue: Problems and improvements with respect to performance of generated code.

Comments

@pcwalton
Copy link
Contributor

pcwalton commented Jul 4, 2014

When we see a direct call to mem::transmute, we should just inline it in the frontend. This has two important benefits, one obvious and one not-so-obvious: (1) it reduces compilation time; (2) it can often avoid one memcpy, because we can simply bitcast the destination instead of bitcasting the source.
@huonw
Copy link
Member

huonw commented Jul 4, 2014

I believe this would be fixed by #12634?

@luqmana
Copy link
Member

luqmana commented Jul 18, 2014

Fixed by #15563.

@luqmana luqmana closed this as completed Jul 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-codegen Area: Code generation I-compiletime Issue: Problems and improvements with respect to compile times. I-slow Issue: Problems and improvements with respect to performance of generated code.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pcwalton @luqmana @huonw