Would be great if somebody could create a list of all them, comparisions, etc in a single page for arm, mips, x86, etc.. Explaining which compiler uses what and so on.
Robin: i think that may be helpful for your project too. But i think this document can be helpful to others too. Would be great to also have a collection of binaries demonstrating every calling convention, so we can use it as a test suite to implement automatic detrction of calling conventions in the code analysis lib in r2. The idea is that the decompiler will work with the info given by the anal engine instead of manually parsing opcodes at thendecompiler code. On Dec 16, 2010, at 9:04 AM, Robin Vossen <[email protected]> wrote: > I think it might be a good idea to also add Ellipsis as a calling > convention. Since it's a bit like one (and a lot of Decompilers use > it) > http://www.tilander.org/aurora2/Exploring_the_ellipsis_construct/comments.html > > Cheers, > Robin > > On 15 December 2010 19:16, Jakub Zawadzki <[email protected]> wrote: >> On Wed, Dec 15, 2010 at 07:15:27PM +0100, pancake wrote: >>> Thanks. Do somebody know if there's a similar list for ARM and MIPS? >> >> ARM ABI: >> http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042d/IHI0042D_aapcs.pdf >> >> Cheers. >> _______________________________________________ >> radare mailing list >> [email protected] >> http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org >> > > > > -- > Kind Regards, > Robin Vossen > > Please avoid sending me Word, Excel or PowerPoint attachments. See > http://www.gnu.org/philosophy/no-word-attachments.html > _______________________________________________ > radare mailing list > [email protected] > http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org > _______________________________________________ radare mailing list [email protected] http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
