This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Testing a speedup to libiberty/concat.c

From: DJ Delorie <dj at redhat dot com>
To: neil at daikokuya dot co dot uk
Cc: ghazi at caip dot rutgers dot edu, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
Date: Tue, 22 Jul 2003 15:10:43 -0400
Subject: Re: Testing a speedup to libiberty/concat.c
References: <200307221540.LAA16151@caip.rutgers.edu> <20030722190439.GP22306@daikokuya.co.uk>

> Why not put a stpcpy equivalent in libiberty if it's useful?

On systems where stpcpy isn't defined, the system's memcpy/strlen will
(hopefully) be faster than a portable C stpcpy.

We can also speed up concat itself by not using the out-lined
functions, and cache the string lengths, so in the copy loop we can
avoid calling strlen and just call memcpy.  But I think that's only
worth it if it's a hot spot, since it reduces maintainability.

References:
- Testing a speedup to libiberty/concat.c
  - From: Kaveh R. Ghazi
- Re: Testing a speedup to libiberty/concat.c
  - From: Neil Booth

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]