Path: ...!weretis.net!feeder9.news.weretis.net!news.misty.com!news.iecc.com!.POSTED.news.iecc.com!not-for-mail From: John Levine Newsgroups: comp.arch Subject: Re: except what, is Vax addressing sane today Date: Sat, 21 Sep 2024 22:14:12 -0000 (UTC) Organization: Taughannock Networks Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 21 Sep 2024 22:14:12 -0000 (UTC) Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="26255"; mail-complaints-to="abuse@iecc.com" In-Reply-To: Cleverness: some X-Newsreader: trn 4.0-test77 (Sep 1, 2010) Originator: johnl@iecc.com (John Levine) Bytes: 2120 Lines: 22 According to MitchAlsup1 : >In the days before branch prediction having a conditional branch >after each instruction that could have an execution problem was an >extremely poor choice. Thus, exceptions were invented (circa 1958). Oh, it was worse than that. There were instructions like "Divide or Halt" which stopped the computer with an error light on a zero divide. >Many (most, nearly all) processor architectures have notoriously >bad exception delivery to a point of control that can deal with >the problem at hand. Some of us remember imprecise itnterrupts and the OS/360 S0C0 completion code. But you are in general right, it makes more sense to keep the computer running in the normal case and provide slow ways to recover from failures and do something else. -- Regards, John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly