Skip to content

Add a few more integer ops "under consideration". #63

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
wants to merge 1 commit into from

Conversation

sunfishcode
Copy link
Member

No description provided.

@jfbastien
Copy link
Member

I'm not sure I agree with all of them, but there doesn't seem to be much harm in considering them. I'm especially wary of adding things which the macro layer would catch, or which the compiler can trivially peephole, but we can have that discussion elsewhere.

@sunfishcode
Copy link
Member Author

I agree that it's not always clear which operators should be included. One possible criteria is that instructions whose expansion would otherwise reference any of the operands multiple times have some value. Clrs, Abs, and SExt all satisfy this criteria. On the other hand, Neg and Bang don't, but those operators are being considered for the opposite reason, because they provide orthogonal fundamentals from which other operations can be synthesized.

@sunfishcode sunfishcode force-pushed the integer-ops-to-consider branch from 88708bf to 2ec85d4 Compare June 1, 2015 16:40
@sunfishcode
Copy link
Member Author

This is subsumed by #121.

@sunfishcode sunfishcode closed this Jun 8, 2015
@sunfishcode sunfishcode deleted the integer-ops-to-consider branch June 8, 2015 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants