Skip to content

feat[codegen]: optimize return buffer handling #4589

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

charles-cooper
Copy link
Member

draft / wip.

What I did

this commit optimizes return buffer handling by allocating to a single location globally (for a function). this helps mem2var since the return offset does not get computed via a phi instruction.

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-->

this commit optimizes return buffer handling by allocating to a single
location globally (for a function). this helps mem2var since the return
offset does not get computed via a phi instruction.
self._return_buffer = self._allocate_return_buffer()

def _allocate_return_buffer(self):
from vyper.codegen.core import calculate_type_for_external_return, get_type_for_exact_size

Check notice

Code scanning / CodeQL

Cyclic import Note

Import of module
vyper.codegen.core
begins an import cycle.
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.

1 participant