musl - Are there plans to support the "old" ABI (apcs-gnu) for ARM?

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+qPFc+kktxA9BkfKr5hzTWdRrstBNdw_GKb-bZBxExbcFgh5g@mail.gmail.com>
Date: Mon, 1 May 2017 16:11:10 -0400
From: mzpqnxow <musl@...qnxow.com>
To: musl@...ts.openwall.com
Subject: Are there plans to support the "old" ABI (apcs-gnu) for ARM?

Hello list,

I've seen it documented in several places that the so-called "old" ABI for
ARM (formally referred to as apcs-gnu, I believe) is not supported by musl,
though I haven't seen any formal explanation as to why. I'm wondering if
this is a design decision that has already been made or if it is just very
low priority on the TODO list- but might be implemented some day. I have a
need for an ARM OABI toolchain that allows me to statically link a good
amount of non-trivial executables and uClibc, glibc, etc. don't work for
me, mainly due to the reliance upon functions in the nss libraries which
need dynamic loading to function correctly.

So I'm curious, will this "old" ARM ABI ever be supported/implemented in
musl or is it dead enough "in the wild" that it will never be implemented?
Also, if there is some way that I am missing something and the old ABI *is*
supported, I'd be happy for someone on the list to point out how I missed
it.

A simple yes/no would be terrific, I don't need a long explanation of how
obsolete and slow the old ABI is- I am painfully aware. But here I am :>

Thanks

Content of type "text/html" skipped

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.