home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.arch:10908 comp.lang.misc:3780
- Newsgroups: comp.arch,comp.lang.misc
- Path: sparky!uunet!spool.mu.edu!umn.edu!uum1!kksys.com!edgar!technix!bret
- From: bret@technix.mn.org (Bret Indrelee)
- Subject: Re: how to advocate new software/hardware features (Re: Hardware Support for Numeric Algorithms)
- Message-ID: <1992Nov19.034325.3864@technix.mn.org>
- Organization: Private System - Saint Paul, MN
- References: <Bxs63J.BxA@exnet.co.uk> <BxtA6v.CE8@mentor.cc.purdue.edu> <id.HJ1V.BTG@ferranti.com>
- Date: Thu, 19 Nov 1992 03:43:25 GMT
- Lines: 24
-
- In article <id.HJ1V.BTG@ferranti.com> peter@ferranti.com (peter da silva) writes:
- >In article <BxtA6v.CE8@mentor.cc.purdue.edu> hrubin@pop.stat.purdue.edu (Herman Rubin) writes:
- >> But it is. The operations often use register arguments and the results
- >> are wanted in registers.
- >
- >What's a register? Most modern compilers ignore "register", or use it as a
- >hint "this is a frequently used value".
- >
- >And how is an inline library part of the language more than a subroutine
- >or an include file?
-
- Which brings up a question I've wondered about. Do any compilers use
- 'register' to indicate that a pointer reference DOESN'T access the
- value?
-
- If so, it once again becomes usefull to use the register keyword,
- as a no-alias. Compiler could optimize knowing that the value isn't
- changed by that weird intervening pointer reference.
-
- -Bret
- --
- ------------------------------------------------------------------------------
- Bret Indrelee | Insanity is all in the mind.
- email: bret@technix.mn.org |
-