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

Implement Garbage Collection Register Analysis Stage #416

Open
tgiphil opened this issue Aug 19, 2017 · 1 comment
Open

Implement Garbage Collection Register Analysis Stage #416

tgiphil opened this issue Aug 19, 2017 · 1 comment

Comments

@tgiphil
Copy link
Member

tgiphil commented Aug 19, 2017

This stage performs a live-in/out range analysis to determine when CPU registers and stack locations hold type references and emits compact data tables with this information. The table can then be used to find all object roots within the stack and CPU registers.

@tgiphil tgiphil added this to the 1.9 Release milestone Aug 19, 2017
@tgiphil tgiphil self-assigned this Aug 19, 2017
@tgiphil tgiphil modified the milestones: 1.9 Release, 2.0 Release Aug 5, 2018
@tgiphil tgiphil changed the title Implement Garbase Collection Register Analysis Stage Implement Garbage Collection Register Analysis Stage Oct 31, 2021
@tgiphil tgiphil modified the milestones: 2.2 Release, Future, 2.4 Release Jan 12, 2023
@tgiphil tgiphil moved this to Todo in Garbage Collection Jul 16, 2023
@tgiphil tgiphil modified the milestones: 2.5 Release, 2.6 Release Jan 18, 2024
@tgiphil
Copy link
Member Author

tgiphil commented Oct 20, 2024

Design Notes:

  1. Garbage Collection SafePoints are where the:
  • Status of all objects can be determined
  • Garbage collection can occur
  • Breakpoints can be inserted
  • Inserted at method prologue/epilogue, loop back edges, and prior to call to new object allocator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant