From -4402836960766584436 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10f5bc,6f6e97a6fdbbf44c X-Google-Attributes: gid10f5bc,public X-Google-Thread: 109fba,6f6e97a6fdbbf44c X-Google-Attributes: gid109fba,public X-Google-Thread: 1014db,6f6e97a6fdbbf44c X-Google-Attributes: gid1014db,public X-Google-Thread: 102b75,6f6e97a6fdbbf44c X-Google-Attributes: gid102b75,public X-Google-Thread: f78e5,6f6e97a6fdbbf44c X-Google-Attributes: gidf78e5,public X-Google-Thread: 110292,6f6e97a6fdbbf44c X-Google-Attributes: gid110292,public X-Google-Thread: 1149ec,6f6e97a6fdbbf44c X-Google-Attributes: gid1149ec,public From: cliffc@crocus.hpl.hp.com (Cliff Click) Subject: Re: And you thought that the Pentium bug was bad! (Get a load of this!) Date: 1995/07/12 Message-ID: #1/1 X-Deja-AN: 106176680 sender: news@hpl.hp.com (HPLabs Usenet Login) references: <3s2las$1br@hustle.rahul.net> <3tud69$cg7@onramp.arc.nasa.gov> organization: Hewlett-Packard Laboratories, Cambridge Research Office newsgroups: comp.std.c,comp.std.c++,comp.lang.c,comp.lang.c++,comp.sys.intel,comp.arch,comp.software.testing lamaster@george.arc.nasa.gov (Hugh LaMaster) writes: > A few weeks ago, Ron Guilmette posted an "amusing" example > of a bug in a common compiler, wondering what the reaction > would be. He anticipated, of course, that the reaction > would be restrained, rather than outrage. Of course, he > was right. After all, it was "only" a compiler bug, and > one which was "only" a problem involving the scope of variables. Perhaps a ray of hope... I immediately checked my compiler against this code. It failed. I fixed it. _I added the code to my test suite_. (all you other compiler writers did too, right? %^) > "Garbage In, Gospel Out." Since this posting came out of a computer, does that mean... :-) Cliff -- Cliff Click Compiler Research Scientist Cambridge Research Office, Hewlett-Packard Laboratories One Main Street, 10th Floor, Cambridge, MA 02142 (617) 225-4915 Work (617) 225-4930 Fax cliffc@hpl.hp.com http://bellona.cs.rice.edu/MSCP/cliff.html