home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!cs.utexas.edu!convex!news.utdallas.edu!corpgate!bnrgate!bmerh85!bcars64a!bqneh3!schow
- From: schow@bqneh3.bnr.ca (Stanley T.H. Chow)
- Subject: Re: trapping speculative ops
- Message-ID: <1992Aug27.005340.6547@bcars64a.bnr.ca>
- Sender: news@bcars64a.bnr.ca (Usenet News)
- Organization: Bell Northern Research Ltd, Ottawa
- References: <GLEW.92Aug25180333@pdx007.intel.com> <CLIFFC.92Aug26084159@medea.rice.edu>
- Date: Thu, 27 Aug 1992 00:53:40 GMT
- Lines: 26
-
- In article <CLIFFC.92Aug26084159@medea.rice.edu> cliffc@rice.edu (Cliff Click) writes:
- >Let every register have some extra "trap" bits.
- >A read of the register with it's trap bits set, causes the exception.
- >A write to the register sets the trap bits according to the success of
- >the operation.
- >
- >With this design, exceptions are triggered at the START of some operation,
- >instead of in the middle of it.
-
- Very nice model, but what to do about saving and restoring registers
- across subroutine call, interupts, etc.?
-
- >Pre-fetch for long-distance memory can be implemented with a simple LOAD.
- >If a page fault is required for the LOAD the fault is delayed until the
- >register is used. If the pre-fetch is speculative, no page fault occurs.
-
- Presumably, the prefetch will use a different opcode, or do you mean all
- references should behave like this?
-
-
-
- --
- Stanley Chow InterNet: schow@BNR.CA
- Bell Northern Research UUCP: ..!uunet!bnrgate!bqneh3!schow
- (613) 763-2831
- Me? Represent other people? Don't make them laugh so hard.
-