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

Remove size parameters from input and output arguments to llvm_symexec #127

Closed
atomb opened this issue Apr 11, 2016 · 1 comment
Closed

Remove size parameters from input and output arguments to llvm_symexec #127

atomb opened this issue Apr 11, 2016 · 1 comment
Assignees
@atomb
Labels
obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing wontfix Closed issues that we decided not to fix, but are still potentially relevant

Comments

@atomb
Copy link
Contributor

atomb commented Apr 11, 2016

These parameters aren't strictly necessary given the allocation sizes passed as the first argument. We can require that the inputs match the allocated sizes exactly, and return the entire allocated region for each output. This would match the behavior of java_symexec.
@atomb atomb mentioned this issue Apr 11, 2016
Closed
@atomb atomb self-assigned this Jun 7, 2016
@atomb atomb added the obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing label Apr 2, 2019
@atomb atomb added the wontfix Closed issues that we decided not to fix, but are still potentially relevant label May 20, 2019
@atomb
Copy link
Contributor Author

atomb commented May 20, 2019

We're about to merge a PR that removes llvm_symexec.

@atomb atomb closed this as completed May 20, 2019
brianhuffman pushed a commit that referenced this issue Apr 26, 2021
Merge pull request #127 from GaloisInc/faster-typechecker
2109f18 
Avoid calling slow `typeInferComplete` on already-typechecked terms.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@atomb atomb

Labels
obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing wontfix Closed issues that we decided not to fix, but are still potentially relevant
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@atomb