Re: Calling conventions (particularly 32-bit ARM)

On 10/01/2025 20:19, Thomas Koenig wrote:

David Brown <david.brown@hesbynett.no> schrieb:
 

How many people actually want to use code where some functions are
called with an incorrect number of parameters?  Such code is /broken/.

 Agreed (at least in priciple).
 

If it ever gave results that the original users were happy with, it is
by luck - no matter what ABI you have for your new architecture and new
tools, it's pure luck whether things work or not in any sense.

 It gets worse when the code in question has been around for decades,
and is widely used.  Some ABIs, such as the x86-64 psABI, are very
forgiving of errors.
 

So the best you can do for your prospective customers is tell them that
you prioritise the results for correct code and help them with tools to
find mistakes in their ancient broken code.

 Now, you can also tell them to use LTO for checks for any old
software.
  Excuses are running out.

Yes, exactly.
I saw somewhere a quotation that backwards compatibility just means repeating the same old mistakes.  Backwards compatibility /is/ important, but so is trying to improve coding practices!