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

Get rid of result and effect #120

Open
langston-barrett opened this issue Feb 15, 2019 · 1 comment
Open

Get rid of result and effect #120

langston-barrett opened this issue Feb 15, 2019 · 1 comment
Labels
enhancement

Comments

@langston-barrett
Copy link
Contributor

Instructions are manually specified as either value- or effect-producing with result and effect, respectively. This is tedious and error-prone, such information should be specified in one big lookup table (function) keyed on (with input type) Instr.
@langston-barrett
Copy link
Contributor Author

I was just bit by this again when implementing cmpxchg: I ended up debugging extractval for a while because it was encountering errors propagated from the fact that I spuriously marked cmpxchg as an effect rather than result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@langston-barrett