Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!ames!cit-vax!news
From: news@cit-vax.UUCP
Newsgroups: comp.arch,comp.sys.misc
Subject: Re: 01/31/87 Dhrystone Results and Source
Message-ID: <1738@cit-vax.Caltech.Edu>
Date: Mon, 9-Feb-87 00:57:14 EST
Article-I.D.: cit-vax.1738
Posted: Mon Feb  9 00:57:14 1987
Date-Received: Tue, 10-Feb-87 02:05:44 EST
References: <2348@homxb.UUCP> <15203@onfcanim.UUCP> <293@ames.UUCP> <2366@homxb.UUCP> <112@winchester.mips.UUCP>
Reply-To: jon@oddhack.UUCP (Jon Leech)
Organization: California Institute of Technology
Lines: 18
Xref: watmath comp.arch:307 comp.sys.misc:330

Organization : California Institute of Technology
Keywords: Benchmark, C, performance measurement, strcpy
From: jon@oddhack.Caltech.Edu (Jon Leech)
Path: oddhack!jon

In article <112@winchester.mips.UUCP> mash@winchester.UUCP (John Mashey) writes:
>b) STRCPY: we've seen strcpy take up to 30% of the execution time.
>Does anybody have any real nubmers of real programs on the real usage
>patterns for the str* and mem* routines? 

	The text editor I maintain (which bears no relationship to any
variant of EMACS, incidentally), runs ~5-10% strcpy on a 4.2 BSD Vax 780,
in average use (according to gprof). Said usage could be reduced by perhaps
2x if I spent the time to clean up the code.

    -- Jon Leech (jon@csvax.caltech.edu || ...seismo!cit-vax!jon)
    Caltech Computer Science Graphics Group
    __@/