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

Extract static source information for runtime target code introspection #8

Open
ahueck opened this issue Sep 3, 2020 · 0 comments
Open

Extract static source information for runtime target code introspection #8

ahueck opened this issue Sep 3, 2020 · 0 comments
Labels
enhancement New feature or request
Milestone
Establish Feature...

Comments

@ahueck
Copy link
Contributor

ahueck commented Sep 3, 2020

Currently, TypeART uses __builtin_return_address(0) to find the address location of where the allocation occurred

Alternatively, (i) during compilation each allocation is tagged with a unique ID, (ii) the id's are passed as arguments to the callbacks, and (iii) the ID and other useful (debug) information are serialised for look-ups in the runtime

The serialisation should happen as json/yaml, see preliminary implementation in feat/sc20
@ahueck ahueck added the enhancement New feature or request label Sep 3, 2020
@ahueck ahueck added this to the Establish Feature Parity milestone Sep 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Establish Feature Parity
Development

No branches or pull requests
1 participant
@ahueck