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

Need to implement Definition for Allocating/Freeing memory #76

Open
CodyFagley opened this issue Jul 2, 2021 · 1 comment
Open

Need to implement Definition for Allocating/Freeing memory #76

CodyFagley opened this issue Jul 2, 2021 · 1 comment
Labels
duplicate This issue or pull request already exists enhancement New feature or request help wanted Extra attention is needed

Comments

@CodyFagley
Copy link
Member

See this Source Code

The referenced C++ code above points at where the assembly function call is made for _x_alloc. Currently, that call is withheld from the cross compiler's generated assembly files, because there is no backend definition for _x_alloc yet. Once that is authored, the addInstruction() procedure call on L59 (of the above file) should be uncommented. Once that is done, memory will be dynamically allocating correctly (albeit unoptimized) and data types can continue in development.
@CodyFagley CodyFagley added enhancement New feature or request help wanted Extra attention is needed labels Jul 2, 2021
@CodyFagley CodyFagley changed the title Need to implement assembly-level Definition for Allocating/Freeing memory Need to implement Definition for Allocating/Freeing memory Jul 23, 2021
@CodyFagley CodyFagley added the duplicate This issue or pull request already exists label Jul 27, 2021
@CodyFagley
Copy link
Member Author

Added Duplicate label, because this has been a persistent issue for 1.5 years now.
Issues for Memory Allocation are piling up and need to be addressed soon for the language development to proceed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate This issue or pull request already exists enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CodyFagley