| Deutsch English Français Italiano |
|
<2025Jan14.190229@mips.complang.tuwien.ac.at> View for Bookmarking (what is this?) Look up another Usenet article |
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: Tue, 14 Jan 2025 18:02:29 GMT Organization: Institut fuer Computersprachen, Technische Universitaet Wien Lines: 29 Message-ID: <2025Jan14.190229@mips.complang.tuwien.ac.at> References: <vlgngv$1ks4a$1@dont-email.me> <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> <a0867899b693a1bc2579ec7cc25d676c@www.novabbs.org> <6DghP.566840$EYNf.141529@fx11.iad> <f95f0786b4a409456e30647609f98ecf@www.novabbs.org> <vquhP.274447$2xE6.129326@fx18.iad> <20250114164128.00007318@yahoo.com> Injection-Date: Tue, 14 Jan 2025 19:13:04 +0100 (CET) Injection-Info: dont-email.me; posting-host="21c41fe4e7eafbd235f793cff3b59f55"; logging-data="2653381"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+OWmHQIGjov1VneKN97bFU" Cancel-Lock: sha1:yF1cRy+QU1nzFGGne2QthxePVio= X-newsreader: xrn 10.11 Bytes: 2687 Michael S <already5chosen@yahoo.com> writes: >On Tue, 14 Jan 2025 14:22:19 GMT >scott@slp53.sl.home (Scott Lurndal) wrote: >> Clearly there are programmers who wish to be able to detect >> certain exceptions, and POSIX allows programmers to >> select that behavior. > >Raising of FP exceptions is orthogonal to question of one instruction >vs library call. If anything, when exceptions are enabled, with >single-instruction implementation it is probably easier for exception >handler to find the reason and generate useful diagnostics. It seems to me that "raise an exception" is in the IEEE 754 sense (by default set a sticky flag in an internal register), not in the C sense of raising a signal. AFAIK you can tell the system to produce a signal for some exceptions, but the default on Linux is not to. >As to what POSIX allows, on the manual page that you quoted I see no >indication that implementation is required to give to programmer to >select this or that behavior. I read it like implementation is allowed >to make the choice fully by itself. And if it is friendly, it can give the programmer a compiler option to select between the variants. - anton -- 'Anyone trying for "industrial quality" ISA should avoid undefined behavior.' Mitch Alsup, <c17fcd89-f024-40e7-a594-88a85ac10d20o@googlegroups.com>