Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter
From: peter@ficc.ferranti.com (Peter da Silva)
Newsgroups: comp.arch
Subject: Re: bizarre instructions
Message-ID: <8UQ9CL7@xds13.ferranti.com>
Date: 26 Feb 91 16:46:03 GMT
References: <10244@dog.ee.lbl.gov> <1991Feb25.203629.5059@linus.mitre.org> <10278@dog.ee.lbl.gov> <22605:Feb2608:04:5391@kramden.acf.nyu.edu>
Reply-To: peter@ficc.ferranti.com (Peter da Silva)
Organization: Xenix Support, FICC
Lines: 12

In article <22605:Feb2608:04:5391@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> In practice this isn't such a big problem. Joe just writes the code in
> several different ways (he has to, if he wants a fighting chance) and
> uses #ifdef or something similar to select the right solution for each
> machine. But this is still a pain.

Yes. It's even more of a pain than just #ifdefing a bunch of inline
assembly. So why not just do that for all the obscure instructions
and have done with it?
-- 
Peter da Silva.  `-_-'  peter@ferranti.com
+1 713 274 5180.  'U`  "Have you hugged your wolf today?"