CN VIP: Add support for memcpy & proxy #694
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dc-mak
commented
Nov 6, 2024
dc-mak
force-pushed
the
cn-vip-memcpy
branch
5 times, most recently
from
54514c6 to
67acca3
Compare
dc-mak
commented
Nov 6, 2024
This commit hooks into an existing place for assigning function types to proxy functions. It assumes that memcpy's type is expressible in CN, which is true-ish for now, but may not remain so if we want to support round-trip for pointers without provenance in byte values, and thus need a "special type" or more arbitrary set of operations on the typing context to support. It also removes some legacy/mostly unused code around partial evaluation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit hooks into an existing place for assigning function types to proxy functions. It assumes that memcpy's type is expressible in CN, which is true-ish for now, but may not remain so if we want to support round-trip for pointers without provenance in byte values, and thus need a "special type" or more arbitrary set of operations on the typing context to support.