Xref: utzoo comp.lang.c++:2097 comp.lang.c:14330 comp.lang.forth:659 comp.lang.fortran:1521 comp.lang.misc:2175 comp.arch:7338
Path: utzoo!attcan!uunet!husc6!mailrus!nrl-cmf!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c++,comp.lang.c,comp.lang.forth,comp.lang.fortran,comp.lang.misc,comp.arch
Subject: Re: Assembly or ....
Message-ID: <8993@smoke.BRL.MIL>
Date: 28 Nov 88 10:48:54 GMT
References: <1388@aucs.UUCP> <729@convex.UUCP> <1961@crete.cs.glasgow.ac.uk> <6529@june.cs.washington.edu> <1031@l.cc.purdue.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 8

In article <1031@l.cc.purdue.edu> cik@l.cc.purdue.edu (Herman Rubin) writes:
>... on the various machines I know, there are operations
>I want to use about which the compiler knows nothing.

There are many of us who don't feel obligated to make use of every
little whiz-bang feature that hardware designers have so thoughtfully
provided.  Life is too short to spend it in an effort to accommodate
hardware quirks.