Re: [bug-gnulib] Re: speed up gnulib-tool a bit

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Bruno Haible on 9/18/2006 9:20 AM:
>> I think it may be possible to shave off another good part, but the next
>> changes probably have a higher source code change to improvement ratio
>> (caching func_lookup_file results could help; or rewriting func_get_*
>> to work on lists of modules; both seem like not too high hanging fruit).
> 
> Uhh, I would be a bit reluctant to apply the second type of changes, since
> it changes the program structure for no other reason than speed. The major
> bottleneck at this time are the autom4te / m4 invocations after gnulib-tool.
> (I'm turning off autom4te's caching in my ~/.autom4te.cfg since temporary
> directories would be acceptable for me in /tmp, but not in the middle
> of my source code directories.)

Please reconsider.  For example, when developing on cygwin, the speed of
autom4te/m4 invocations is in the noise compared to the speed penalty of
extra forking  of poor shell coding.  Just because your platform has
faster forks than the computational bottleneck of autom4te does not mean
that your execution profile is universal to other platforms.

- --
Life is short - so eat dessert first!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFD+je84KuGfSFAYARAhOHAKCBJMnb+GJplhQGzkuXf7LPyyOmwACaA3VH
22r6N+BjLuFZjcBzjcTKTRg=
=EgvV
-----END PGP SIGNATURE-----