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

Analyze size of generated RecordFlux code #909

Closed
jklmnn opened this issue Jan 18, 2022 · 2 comments
Closed

Analyze size of generated RecordFlux code #909

jklmnn opened this issue Jan 18, 2022 · 2 comments
Assignees
@jklmnn

Comments

@jklmnn
Copy link
Member

jklmnn commented Jan 18, 2022

Since RecordFlux is intended to be used in an embedded context we should analyze the generated code size.

The code size will be calculated by the size of the .text section of the generated binary minus the size of the .text section of a reference binary that is built from an empty main procedure.

Additionally the impact of the pragmas Restrictions (No_Exception) and Restrictions (No_Secondary_Stack) will be analyzed.
@jklmnn jklmnn self-assigned this Jan 18, 2022
@treiher
Copy link
Collaborator

treiher commented Jan 18, 2022

I suppose this ticket is intended for the analysis and the realization will be done in #908?

@jklmnn
Copy link
Member Author

jklmnn commented Jan 18, 2022

I overlooked #908. I'll close this ticket then.

@jklmnn jklmnn closed this as completed Jan 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jklmnn jklmnn

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jklmnn @treiher