Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!cit-vax!ucla-cs!zen!ucbvax!VENUS.YCC.YALE.EDU!leichter
From: leichter@VENUS.YCC.YALE.EDU ("Jerry Leichter")
Newsgroups: comp.os.vms
Subject: re: where is C$MEMFUNC
Message-ID: <8709121708.AA23403@ucbvax.Berkeley.EDU>
Date: Sat, 12-Sep-87 10:59:00 EDT
Article-I.D.: ucbvax.8709121708.AA23403
Posted: Sat Sep 12 10:59:00 1987
Date-Received: Sun, 13-Sep-87 09:50:14 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: "Jerry Leichter" <leichter@venus.ycc.yale.edu>
Organization: The ARPA Internet
Lines: 20


	On the subject of the memxxx functions here is a bug. We are running
	on one of those strange combinations mentioned in earlier articles.
	We have VMS 4.5 with a C 2.3 compiler and RTL on a uVAX.

	It would appear that memset() does not save/restore the registers.
	Here is a sample program:

		[Example program elided; it shows R6 being trashed]

The fact that you HAVE memset at all on a VMS V4.5 system means you got a V4.6
VAXCRTL from somewhere.  My guess is that you were a field test site for VAX C
and are still using the FT VAXCRTL.  Guess what:  A bug found (and fixed)
during field test was that memset wasn't saving the right registers.

							-- Jerry

PS:  If you were NOT a FT site, you got your code "under the table".  Don't
look for sympathy in that case....
------