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.

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

feat[test]: remove memory mocker #4005

Merged

Conversation

charles-cooper
Copy link
Member

it doesn't really find bugs (since the calling convention was redone in 0.3.0) and we have better ways to analyze memory now since the introduction of the venom pipeline.

What I did

How I did it

How to verify it

Commit message

Commit message for the final, squashed PR. (Optional, but reviewers will appreciate it! Please see our commit message style guide for what we would ideally like to see in a commit message.)

Description for the changelog

Cute Animal Picture

Put a link to a cute animal picture inside the parenthesis-->

it doesn't really find bugs (since the calling convention was redone in
0.3.0) and we have better ways to analyze memory now since the
introduction of the venom pipeline.
@fubuloubu
Copy link
Member

we have better ways to analyze memory now since the introduction of the venom pipeline

Link?

@charles-cooper
Copy link
Member Author

we have better ways to analyze memory now since the introduction of the venom pipeline

Link?

see for instance #3941, we don't even allocate physical memory locations in the frontend anymore when venom pipeline is enabled. the plan is to do memory allocation as a much later pass in venom after memory analysis has been performed and redundant memory allocations removed.

@charles-cooper charles-cooper merged commit 6c272b7 into vyperlang:master May 6, 2024
149 checks passed
@charles-cooper charles-cooper deleted the feat/remove-memorymock-tests branch May 6, 2024 15:57
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.

None yet

2 participants