Repository navigation
Add a Developer Resources section with links to ABI documentation - #3047
Conversation
|
Thanks for the PR. If you have write access, feel free to merge this PR if it does not need reviews. You can request a review using |
| A 2018 version of the document "Qualcomm Hexagon Application Binary Interface" is available at | ||
| <https://docs.qualcomm.com/doc/80-N2040-23/80-N2040-23_REV_K_Qualcomm_Hexagon_Application_Binary_Interface_User_Guide.pdf>. |
There was a problem hiding this comment.
@androm3da I know Hexagon undergoes active development, is this the most recent spec?
There was a problem hiding this comment.
I think there was one published this week - I'll find it.
There was a problem hiding this comment.
https://docs.qualcomm.com/doc/80-N2040-23/
Since that PDF was published, Qualcomm has shifted towards webpage manuals. So I think this link should be where new ABI spec updates get published in the future.
| There are a few relevant documents for PowerPC ABI: | ||
|
|
||
| * [_System V Application Binary Interface: PowerPC Processor | ||
| Supplement_](http://refspecs.linux-foundation.org/elf/elfspec_ppc.pdf) is the original 32-bit |
There was a problem hiding this comment.
| Supplement_](http://refspecs.linux-foundation.org/elf/elfspec_ppc.pdf) is the original 32-bit | |
| Supplement_](https://refspecs.linuxfoundation.org/elf/elfspec_ppc.pdf) is the original 32-bit |
found a non-borked https url
There was a problem hiding this comment.
That's the one I was looking at too, updated it now
|
|
||
| #### MIPS | ||
|
|
||
| TODO link to o32, n32, and n64 if possible. |
There was a problem hiding this comment.
I looked into this a couple of years ago, and the best I found was:
o32: 3rd edition from February 1996: https://refspecs.linuxfoundation.org/elf/mipsabi.pdf
n32: "MIPSpro™ N32 ABI Handbook" from October 2002: https://irix7.com/techpubs/007-2816-005.pdf
n64: "MIPSpro™ 64-Bit Porting and Transition Guide": https://irix7.com/techpubs/007-2391-006.pdf
There was a problem hiding this comment.
I think the second doc also defines n64. Added all of these, thanks
| Supplement_](http://refspecs.linux-foundation.org/elf/elfspec_ppc.pdf) is the original 32-bit | ||
| PowerPC ABI specification. | ||
| * [_Power Architecture™ 32-bit Application Binary Interface Supplement 1.0 - Linux® & | ||
| Embedded_](https://example61560.wordpress.com/wp-content/uploads/2016/11/powerpc_abi.pdf) is the |
There was a problem hiding this comment.
|
|
||
| #### SPARC | ||
|
|
||
| TODO |
There was a problem hiding this comment.
Available here: https://sparc.org/technical-documents/specifications/. "SCD 2.4.1" is the latest, with the 32-bit section just containing the (minor) changes from the previous version, "SPARC psABI 3.0".
There was a problem hiding this comment.
maybe name the page platform-specifics.md, though am thinking maybe this info should live in rustc book, which has platform-specific details
There was a problem hiding this comment.
I figured this can hold more than only platform specifics (even though that's all this PR adds), since we didn't really have a home for other things like that currently. Also considered the rustc book but I think this may be a bit niche for something user-facing, though I don't know what's best.
There was a problem hiding this comment.
Developer Resources feels too general as a title, like for example, some of the other appendices could fit in that title
There was a problem hiding this comment.
That's fair, since the whole thing is really a developer resource. Renamed to "additional resources" which I think is a bit better, though it still could match other appendix entries.
| PowerPC64 targets. | ||
| * [_64-bit ELF V2 ABI Specification: Power | ||
| Architecture_](https://openpower.foundation/specifications/64bitelfabi/) is the replacement ABI | ||
| and used by default on most PowerPC64 targets. |
There was a problem hiding this comment.
I think the links look OK. It's always a pain to dredge up these documents.
We need to refer to these rather often, but there hasn't been a common place to locate this information.
|
Thanks all for taking a look |
We need to refer to these rather often, but there hasn't been a common place to locate this information.