-
Notifications
You must be signed in to change notification settings - Fork 98
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.
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
Specify the ABI of -rt
crates in the Rust embedded ecosystem
#418
Comments
Sounds like a good idea. Should we do our specifications as RFCs like the IETF does, or should we have some sort of |
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? |
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-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: