Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.arch
Subject: Re: Calling conventions (particularly 32-bit ARM)
Date: Tue, 14 Jan 2025 00:14:09 -0800
Organization: None to speak of
Lines: 31
Message-ID: <874j21ak32.fsf@nosuchdomain.example.com>
References: <vlgngv$1ks4a$1@dont-email.me>
	<4903307dfcce354508c9fc016a4c1ea1@www.novabbs.org>
	<jwv34htql17.fsf-monnier+comp.arch@gnu.org>
	<2025Jan8.230846@mips.complang.tuwien.ac.at>
	<jwvr05cq4tx.fsf-monnier+comp.arch@gnu.org>
	<2025Jan9.082357@mips.complang.tuwien.ac.at>
	<vlqm0d$27bfb$1@paganini.bofh.team>
	<2025Jan10.112523@mips.complang.tuwien.ac.at>
	<6be6d207cf7386fb66d47f2fe619df71@www.novabbs.org>
	<vm3kf2$1t0s1$1@dont-email.me>
	<6248473300a9fc0fd964c635510f510d@www.novabbs.org>
	<TXfhP.642290$Uup4.301463@fx10.iad>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Tue, 14 Jan 2025 09:14:10 +0100 (CET)
Injection-Info: dont-email.me; posting-host="b949980cf0e823ed5c5fd65edca1d2ec";
	logging-data="2458227"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+rGxWAIrWal8LQEdDIER1z"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:ZFovI3mTVUUqQeK6yLFlEZG2dCM=
	sha1:Qv0j+mO0OsDcsUMXBrbEiOM2Yd0=
Bytes: 2607

scott@slp53.sl.home (Scott Lurndal) writes:
> mitchalsup@aol.com (MitchAlsup1) writes:
>>On Mon, 13 Jan 2025 18:02:10 +0000, Thomas Koenig wrote:
>>
>>> MitchAlsup1 <mitchalsup@aol.com> schrieb:
>>>
>>>> errno is an atrocity all by itself; single handedly preventing
>>>> direct use of SIN(), COS(), TAN(), ATAN(), exp(), ln(), pow()
>>>> as instructions.
>>>
>>> Fortunately, the C standard does not require errno to be set
>>> for these functions.  Apple, for example, does not do so.
>>
>>Nor will I.
>
> POSIX does, however, require errno to be set conditionally
> based on an application global variable 'math_errhandling'.

math_errhandling is specified by ISO C, starting with the 1999 edition
of the standard.

The value of math_errhandling is determined by the implementation, not
by the application.  "The value of math_errhandling is constant for the
duration of the program."  (A compiler could provide an option to set
the value; I don't know whether any do so.)

https://www.iso-9899.info/n1570.html#7.12

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */