[Runtime] Parameterize constants in MISRA-C runtime#5062
Closed
liangfu wants to merge 1 commit intoapache:masterfrom
Closed
[Runtime] Parameterize constants in MISRA-C runtime#5062liangfu wants to merge 1 commit intoapache:masterfrom
liangfu wants to merge 1 commit intoapache:masterfrom
Conversation
Change-Id: I5a0a6180d608ec9aa4606d46bd289641aa251874
9 tasks
Member
|
Thanks @liangfu I think perhaps we could have a even better solution. By asking for a single stack to allocate these data structures from, which accounts for the memory for the containers as well as Tensors. In this way we won't need special magic constants for the runtime. |
Member
Author
|
This is closed, since we are going to implement a memory container that returns addresses from a single stack. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As part of #5060, this PR parameterize constants in MISRA-C runtime proposed in PR #3934 .
Here is a brief statistics on running the test module:
Here is a brief statistics on running the demo module:
The memory footprint is larger in demo module, because MISRA-C runtime takes max size for all layers.
@ajtulloch @tmoreau89 Please review.