On Tue, 22 Apr 2008, Ralf Wildenhues wrote:
To put some sort of proof to my claims, here's what I get building GM
unoptimized (CFLAGS=-g) on GNU/Linux with Libtool 2.2.2. and current
master (all timings best of three):
[ stuff removed ]
Looks like a small but definite improvement to me.
* Bob Friesenhahn wrote on Tue, Apr 22, 2008 at 05:18:34PM CEST:
On Tue, 22 Apr 2008, Ralf Wildenhues wrote:
Can you please check whether
libtool --tag=CXX --config
is identical for each of the builds you timed?
It is really not as easy as you presume for me to relibtoolize
On Mon, 21 Apr 2008, Ralf Wildenhues wrote:
If they were lower in between, and since increased, there must have been
at least one regression along the way. Can you use git bisect to
identify one?
Remember that you fixed an expr-related bug which was impacting
FreeBSD and causing an error
* Bob Friesenhahn wrote on Mon, Apr 21, 2008 at 05:14:00PM CEST:
On Mon, 21 Apr 2008, Ralf Wildenhues wrote:
If they were lower in between, and since increased, there must have been
at least one regression along the way. Can you use git bisect to
identify one?
Remember that you fixed an
Since libtool performance has become a concern, I have been measuring
build times for a reference project in order to evaluate progress. I
selected a project at random and ended up with one called
'GraphicsMagick'. I am testing the build on a FreeBSD 7.0 system with
two 2.4GHz Intel Xeon
Hi Bob,
* Bob Friesenhahn wrote on Mon, Apr 21, 2008 at 12:55:08AM CEST:
I am saddened to report that as of yesterday, build times for git
libtool are now similar to libtool 2.2.2. This is not to say that there
has not been progress. The reported system times have gone down (from
113 to
