Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!sun-barr!texsun!texbell!vector!attctc!kcdev!pars!cpsolv!rhg
From: rhg@cpsolv.UUCP (Richard H. Gumpertz)
Newsgroups: comp.arch
Subject: Re: uninitialized variable checking
Message-ID: <171@cpsolv.UUCP>
Date: 6 Sep 89 04:42:05 GMT
References: <12.filbo@gorn.santa-cruz.ca.us> <4322@druhi.ATT.COM> <3248@itivax.iti.org> <26762@gumby.mips.COM>
Reply-To: rhg@cpsolv.uucp (Richard H. Gumpertz)
Organization: Computer Problem Solving, Leawood, Kansas
Lines: 8

If you are interested in use of error detecting codes for detecting
uninitialized variables plus a lot more, you might want to hunt down
a copy of my thesis: "Error Detection with Memory Tags", Carnegie-Mellon
University, 1981 (CMU Computer Science Tech. Report CMU-CS-84-122).  If
nothing else, it cites some historical use of parity for detecting both
uninitialized variables and type mismatches.

		Richard H. Gumpertz