Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: "Lete2??s Stop Bashing C" Date: Wed, 07 Dec 2016 09:22:12 -0800 Organization: None to speak of Lines: 22 Message-ID: References: <8f359715-238c-42b4-b53f-5c5511725fdb@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="f53e7a1e34684316d0e01429e9e9bbea"; logging-data="2193"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/XugceeGgBKoTd4tcJwcBz" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:tHI1DW3+2+e4fDqUH0i7LWbDD5E= sha1:/bOiidnCShKfJB6LjWFJk7ifO8s= Xref: csiph.com comp.lang.c:98274 jacobnavia writes: > Le 07/12/2016 á 08:41, Ike Naar a écrit : >> The 'overflow' variants the of arithmetic instructions (addlv, >> mullv, sublv etc.) signal an overflow exception, but they do not >> set an overflow flag, so I don't see how one could efficiently >> "test the overflow flag". > > So what? > Any overflow trap sets that flag! Sets what flag? My understanding (based mostly on reading this discussion) is that the Alpha doesn't have a hardware "overflow flag". Are you talking about dedicating some memory location for use as an overflow flag, controlled by software? [...] -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"