https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118330
--- Comment #2 from David Brown <david at westcontrol dot com> --- (In reply to Andrew Pinski from comment #1) > Note you could also work with the upstream arm eabi definition here: > https://github.com/ARM-software/abi-aa Yes, that is certainly a possibility I considered. I also considered registering an issue with the "ARM GNU Toolchain" folks here: <https://developer.arm.com/Tools%20and%20Software/GNU%20Toolchain> That's the group that puts together the most commonly used packaging of gcc for embedded ARM, along with libraries and all the associated code generation tools. However, I believe this could be a feature that would be of use in many gcc targets. And I thought it best to at least talk about the practical aspects of implementation here first. If this is something that the gcc developers can see being useful on multiple targets and can be implemented as an extension (such as using a function attribute rather than as a full new ABI), then that would be great from my viewpoint. If, on the other hand, the gcc developers feel this is a major change and should only come about via a new ABI from ARM, then the "abi-aa" github project is the route to go. The end results that way would be better too - no need for function attributes, and compatibility across different compilers. I suspect, however, that that route would take much longer to lead to results.
