Path: csiph.com!x330-a1.tempe.blueboxinc.net!aioe.org!news.glorb.com!dotsrc.org!filter.dotsrc.org!news.dotsrc.org!not-for-mail From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Newsgroups: comp.os.vms,alt.sys.pdp11,comp.sys.dec,vmsnet.pdp-11 Subject: Re: Y3K for PDP-11 Operating Systems Message-ID: Date: 10 May 2011 08:29:20 -0500 References: <4d99c3b6$0$23756$14726298@news.sunsite.dk> <4dc032d4$0$313$14726298@news.sunsite.dk> <7d287cc3-4605-49a0-826e-fb92fc14e98d@j28g2000vbp.googlegroups.com> <92bjl8F19sU1@mid.individual.net> <92d114Fhm7U1@mid.individual.net> kLbiJT1og, Johnny Billquist writes: > > Hmm. Memory alignment issues... Good point. > Otherwise, I'm also pretty sure that a function like strcpy() is much > better to do on your own, as the VAX really don't have a good way of > implementing that. Doing first a LOCC to get the length, and then a MOVC > to move the string will surely be less efficient than just doing a MOV > followed by a conditional branch to loop... Obviously, for C stuff, > anything dealing with strings is opposed to how a VAX wants things. :-) I never did understand why the VAX C RTL did a LOCC first, instead of a MOVTUC with a straight-through translation table and null escape charater. I assumed MOVTUC was even slower. The need to find that null character, in any case, always seemed to be one more reason to use a better HLL.