Great, I verified that we nearly get the speed back:
When build xz:
libtool-2.4.5 libtool-2.4.2
bash:14s13s
dash:12s11s
// Robert
On 02/10/2015 06:35 PM, Richard Purdie wrote:
On Mon, 2015-02-09 at 23:36 +, Richard Purdie wrote:
On Mon, 2
On Tue, 2015-02-10 at 10:53 +, Gary V. Vaughan wrote:
> On Feb 10, 2015, at 10:35 AM, Richard Purdie
> wrote:
> > On Mon, 2015-02-09 at 23:36 +, Richard Purdie wrote:
> >> On Mon, 2015-02-09 at 13:05 +, Richard Purdie wrote:
> >>> In an effort to get to the bottom of this I made a git
Hi Richard,
On Feb 10, 2015, at 10:35 AM, Richard Purdie
wrote:
> On Mon, 2015-02-09 at 23:36 +, Richard Purdie wrote:
>> On Mon, 2015-02-09 at 13:05 +, Richard Purdie wrote:
>>> In an effort to get to the bottom of this I made a git bisection, timing
>>> the performance of building xz w
Hi Richard,
> On Feb 9, 2015, at 11:36 PM, Richard Purdie
> wrote:
>
> On Mon, 2015-02-09 at 13:05 +, Richard Purdie wrote:
>> In an effort to get to the bottom of this I made a git bisection, timing
>> the performance of building xz with make -j1 using each different
>> libtool.
>>
>> The
On Mon, 2015-02-09 at 23:36 +, Richard Purdie wrote:
> On Mon, 2015-02-09 at 13:05 +, Richard Purdie wrote:
> > In an effort to get to the bottom of this I made a git bisection, timing
> > the performance of building xz with make -j1 using each different
> > libtool.
> >
> > The issues com
On Mon, 2015-02-09 at 13:05 +, Richard Purdie wrote:
> In an effort to get to the bottom of this I made a git bisection, timing
> the performance of building xz with make -j1 using each different
> libtool.
>
> The issues come down to this commit:
>
> http://git.savannah.gnu.org/cgit/libtool.
On 2015-02-09 14:05, Richard Purdie wrote:
> On Mon, 2015-02-09 at 10:45 +0800, Robert Yang wrote:
>> On 02/06/2015 10:46 PM, Bob Friesenhahn wrote:
>>> On Fri, 6 Feb 2015, Robert Yang wrote:
>>>
On 02/06/2015 12:12 PM, Bob Friesenhahn wrote:
> I am not seeing quite the differenc
On Mon, 2015-02-09 at 10:45 +0800, Robert Yang wrote:
> On 02/06/2015 10:46 PM, Bob Friesenhahn wrote:
> > On Fri, 6 Feb 2015, Robert Yang wrote:
> >
> >>
> >>
> >> On 02/06/2015 12:12 PM, Bob Friesenhahn wrote:
> >>> I am not seeing quite the difference between libtool releases that you are
> >>>
On 02/06/2015 10:46 PM, Bob Friesenhahn wrote:
On Fri, 6 Feb 2015, Robert Yang wrote:
On 02/06/2015 12:12 PM, Bob Friesenhahn wrote:
I am not seeing quite the difference between libtool releases that you are
although I see a big slowdown starting with 2.4.3. These timings are for
optimize
On Fri, 6 Feb 2015, Robert Yang wrote:
On 02/06/2015 12:12 PM, Bob Friesenhahn wrote:
I am not seeing quite the difference between libtool releases that you are
although I see a big slowdown starting with 2.4.3. These timings are for
optimized builds of GraphicsMagick on a 12-core GNU/Linux
Hi everybody,
On vr, 2015-02-06 at 10:46 +0100, Peter Rosin wrote:
> On 2015-02-06 10:30, Gary V. Vaughan wrote:
> > Hi Peter,
> >
> >> On Feb 6, 2015, at 9:22 AM, Peter Rosin wrote:
> >>
> >>> On 2015-02-04 15:48, Bob Friesenhahn wrote:
> On Wed, 4 Feb 2015, Robert Yang wrote:
>
> >>
Hi Peter,
On Feb 6, 2015, at 9:46 AM, Peter Rosin wrote:
> On 2015-02-06 10:30, Gary V. Vaughan wrote:
>>> On Feb 6, 2015, at 9:22 AM, Peter Rosin wrote:
>>>
On 2015-02-04 15:48, Bob Friesenhahn wrote:
> On Wed, 4 Feb 2015, Robert Yang wrote:
>
> When reporting a bug, please d
On 2015-02-06 10:30, Gary V. Vaughan wrote:
> Hi Peter,
>
>> On Feb 6, 2015, at 9:22 AM, Peter Rosin wrote:
>>
>>> On 2015-02-04 15:48, Bob Friesenhahn wrote:
On Wed, 4 Feb 2015, Robert Yang wrote:
When reporting a bug, please describe a test case to reproduce it and
include t
Hi Peter,
> On Feb 6, 2015, at 9:22 AM, Peter Rosin wrote:
>
>> On 2015-02-04 15:48, Bob Friesenhahn wrote:
>>> On Wed, 4 Feb 2015, Robert Yang wrote:
>>>
>>> When reporting a bug, please describe a test case to reproduce it and
>>> include the following information:
>>>
>>> host-triplet:
On 2015-02-04 15:48, Bob Friesenhahn wrote:
> On Wed, 4 Feb 2015, Robert Yang wrote:
>
>> When reporting a bug, please describe a test case to reproduce it and
>> include the following information:
>>
>> host-triplet: $host
>> shell: $SHELL
>> compiler: $LTCC
>>
On 02/06/2015 02:12 PM, Bob Friesenhahn wrote:
It is curious that there is more impact for the optimized builds.
Well, it's a constant 5s impact for both optimized and non-optimized -
except for v2.4.3 which looks odd.
Cheers,
--
Peter Johansson
_
On 02/06/2015 12:12 PM, Bob Friesenhahn wrote:
I am not seeing quite the difference between libtool releases that you are
although I see a big slowdown starting with 2.4.3. These timings are for
optimized builds of GraphicsMagick on a 12-core GNU/Linux system using -j 12:
I think that we can
I am not seeing quite the difference between libtool releases that you
are although I see a big slowdown starting with 2.4.3. These timings
are for optimized builds of GraphicsMagick on a 12-core GNU/Linux
system using -j 12:
2.4.2 : 23.613
2.4.3 : 31.697
2.4.4 : 28.236
2.4.5 : 28.514
And he
Hello,
After removing the two lines, libtool 2.4.5 is a little slower than 2.4.2
when using /bin/dash, but it is much slower than in bash, here is the
data when compile xz: (make -j1)
lt-2.4.2 lt-2.4.5(before patched) lt-2.4.5(after patched)
dash 11s 21s
On 02/04/2015 10:48 PM, Bob Friesenhahn wrote:
On Wed, 4 Feb 2015, Robert Yang wrote:
When reporting a bug, please describe a test case to reproduce it and
include the following information:
host-triplet: $host
shell: $SHELL
compiler: $LTCC
compiler f
On Wed, 4 Feb 2015, Robert Yang wrote:
When reporting a bug, please describe a test case to reproduce it and
include the following information:
host-triplet: $host
shell: $SHELL
compiler: $LTCC
compiler flags: $LTCFLAGS
linker: $LD (gnu? $w
Hello,
I've found apart of the reason, for xz:
libtool 2.4.2 2.4.5(before patched) (after patched)
make -j19s 19s11s
Remove the following lines from libtool, then the compile will be
much faster, the problem is the variable like $host, $S
On 02/03/2015 10:31 PM, Bob Friesenhahn wrote:
On Tue, 3 Feb 2015, Robert Yang wrote:
Sorry, I was wrong, tt seems that libtoolize is not the key, but libtool,
when compile cairo-1.12.18:
libtool 2.4.2libtool 2.4.5
configure: 31s32s
compile:54s64s
The lib
On Tue, 3 Feb 2015, Robert Yang wrote:
Sorry, I was wrong, tt seems that libtoolize is not the key, but libtool,
when compile cairo-1.12.18:
libtool 2.4.2 libtool 2.4.5
configure: 31s 32s
compile:54s 64s
The libtool 2.4.5 costs 10 more sec
On 02/02/2015 10:19 PM, Bob Friesenhahn wrote:
On Mon, 2 Feb 2015, Robert Yang wrote:
Hello libtool,
It seems that libtool (2.4.4) has increased the packages build time, after
a rough investigation, it maybe because new libtoolize needs run a m4
command:
Did you time 'libtoolize' and comp
On Mon, 2015-02-02 at 08:19 -0600, Bob Friesenhahn wrote:
> On Mon, 2 Feb 2015, Robert Yang wrote:
> > It seems that libtool (2.4.4) has increased the packages build time, after
> > a rough investigation, it maybe because new libtoolize needs run a m4
> > command:
>
> Did you time 'libtoolize' and
On Mon, 2 Feb 2015, Robert Yang wrote:
Hello libtool,
It seems that libtool (2.4.4) has increased the packages build time, after
a rough investigation, it maybe because new libtoolize needs run a m4
command:
Did you time 'libtoolize' and compare the timings with 2.4.4 to the
release you wer
Hello libtool,
It seems that libtool (2.4.4) has increased the packages build time, after
a rough investigation, it maybe because new libtoolize needs run a m4
command:
# Save the command pipeline results for further use by callers of
# this function.
func_extract_trace_result=`$ECH
28 matches
Mail list logo
