You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-rt crates like cortex-m-rt provide linker scripts with sections and common symbol names that can be used by applications and tooling.
In order for such tooling to be portable across architectures it would be great to specify what kinds of sections and symbols should be exported. This would allow tooling such as flip-lld to work on any architecture (as long as it uses ELF). It can also benefit analysis tools, which can be important on embedded systems.
The text was updated successfully, but these errors were encountered:
Sounds like a good idea. Should we do our specifications as RFCs like the IETF does, or should we have some sort of specifications/spec-0000.md structure do you think?
Going through the RFC process seems generally reasonable. One issue might be discoverability when specifications end up among other more "mundane" RFCs. Maybe we want to have an index of specifications in the readme, or something like that?
-rt
crates likecortex-m-rt
provide linker scripts with sections and common symbol names that can be used by applications and tooling.In order for such tooling to be portable across architectures it would be great to specify what kinds of sections and symbols should be exported. This would allow tooling such as flip-lld to work on any architecture (as long as it uses ELF). It can also benefit analysis tools, which can be important on embedded systems.
The text was updated successfully, but these errors were encountered: