home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!destroyer!ubc-cs!uw-beaver!tera.com!news
- From: bob@tera.com (Bob Alverson)
- Subject: Re: trapping speculative ops (LONG)
- Message-ID: <1992Sep1.152044.12253@tera.com>
- Sender: news@tera.com (News Administrator)
- Reply-To: bob@tera.com
- Organization: Tera Computer Company, Seattle, WA
- References: <1992Aug31.224611.5196@odin.diku.dk>
- Date: Tue, 1 Sep 1992 15:20:44 GMT
- Lines: 26
-
- To quote William Kahan:
-
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
- Exceptions are not errors.
-
- Unless they are handled badly.
-
- In other words, if you think you can roll over and die when you take an exception,
- you are severely restricting hardware and software. In many cases, some fix up
- is desired followed by a return from the exception. Continuing in this way can
- be quite challenging if you have gone too far forward. Values that were around
- may no longer be anywhere to be found. However, an architectural way to guarantee
- that no traps from an operation will occur in the future is nice. DEC's Alpha
- has the sledge-hammer-like trap barrier. Being able to selectively touch off
- traps gives the compiler more control and may allow better pipeline usage.
-
- Bob
-
-