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: [gfortran,patch] Don't call library function for string copying, take 2

From: "François-Xavier Coudert" <fxcoudert at gmail dot com>
To: "Thomas Koenig" <Thomas dot Koenig at online dot de>
Cc: gfortran <fortran at gcc dot gnu dot org>, patch <gcc-patches at gcc dot gnu dot org>
Date: Tue, 11 Jul 2006 15:36:58 +0200
Subject: Re: [gfortran,patch] Don't call library function for string copying, take 2
References: <19c433eb0607040744o491fa334t91f3483a58e7118@mail.gmail.com> <19c433eb0607110111n13da4d4fg292892242d742455@mail.gmail.com> <20060711122657.GA25661@meiner.onlinehome.de>

Another thought: Can you inline compare_string as well, or maybe
only call a library function if the memcmp returned equal?


I have been thinking about that. Doing it completely might be a real
pain, but the option you suggest (emitting memcmp followed by a
library call if need be) sounds good. Although I don't think it's
emitted very often (except explicit calls to strcmp).

FX

References:
- [gfortran,patch] Don't call library function for string copying, take 2
  - From: François-Xavier Coudert
- Re: [gfortran,patch] Don't call library function for string copying, take 2
  - From: François-Xavier Coudert
- Re: [gfortran,patch] Don't call library function for string copying, take 2
  - From: Thomas Koenig

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