Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: anton@mips.complang.tuwien.ac.at (Anton Ertl)
Newsgroups: comp.arch
Subject: Re: Calling conventions (particularly 32-bit ARM)
Date: Thu, 09 Jan 2025 08:38:32 GMT
Organization: Institut fuer Computersprachen, Technische Universitaet Wien
Lines: 15
Message-ID: <2025Jan9.093832@mips.complang.tuwien.ac.at>
References: <vlgngv$1ks4a$1@dont-email.me> <4903307dfcce354508c9fc016a4c1ea1@www.novabbs.org> <ve4rnjpipquiugm3j1831m0a7v0va4lu03@4ax.com> <jwv8qrlql4p.fsf-monnier+comp.arch@gnu.org>
Injection-Date: Thu, 09 Jan 2025 09:46:25 +0100 (CET)
Injection-Info: dont-email.me; posting-host="26ca2a267844a559410fefd8d7bda046";
	logging-data="3457094"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/2V97bhrZUI4IqLtY5ZW/i"
Cancel-Lock: sha1:8sIxvlf4FkgF6JRg5bJGXMa8CJY=
X-newsreader: xrn 10.11
Bytes: 1705

Stefan Monnier <monnier@iro.umontreal.ca> writes:
>AFAIK in these cases the same compiler generates the code for the
>function and for the calls, so it should be pretty much free to use any
>calling convention it likes.

With separate compilation, the compiler does not know which other
compiler generates the code for the caller of a function or the callee
of a function.  ABI Calling conventions exist in order to make code by
different compilers (whether the same language or a different one)
interoperable.

- anton
-- 
'Anyone trying for "industrial quality" ISA should avoid undefined behavior.'
  Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>