stack use improvements (towards nanox execution) #23
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.
attempting to fix the app execution on the nanox (no luck so far)
further improvements to stack frame sizes in the hope that the less efficient ISA caused a recurrence of the 8kb of stack issue, blocking inlining of large functions in the same stack frame and swapping to per-field init of large objects. this doesn't appear to have helped.
testing targets for nanosplus/nanox devices to try and isolate the error from the ISA
thumbv7m-none-eabi
target (addsDIV
andMOD
instructions), this runs correctly in simulator, @yhql tested this still appears to fail on devicethumbv7m-none-eabi
andthumbv6m-none-eabi
targets, both run fine on the physical nanosplus and simulator, suggesting the issue is specific to the nanox OS / hardwarestack frames before:
stack frames after: