Re: [libav-devel] [PATCH 1/3] configure: speed up flatten_extralibs_wrapper()

2018-09-17 Thread avih
( I'm not registered to the list) The changes to unique/resolve/flatten_extralibs are all local to each function. That is, each modified function is a stand-alone drop-in replacement for the original function. flatten_extralibs_wrapper itself was not modified at the original set, but its

Re: [libav-devel] [PATCH 1/3] configure: speed up flatten_extralibs_wrapper()

2018-09-17 Thread James Almer
On 9/17/2018 3:49 PM, Diego Biurrun wrote: > On Sun, Sep 16, 2018 at 11:52:59PM -0300, James Almer wrote: >> From: Avi Halachmi >> >> x50 - x200 faster. > > The set looks very interesting. I've had some ideas on how to speed up > this part of configure already, so I'm doubly happy to see some

Re: [libav-devel] [PATCH 1/3] configure: speed up flatten_extralibs_wrapper()

2018-09-17 Thread Diego Biurrun
On Sun, Sep 16, 2018 at 11:52:59PM -0300, James Almer wrote: > From: Avi Halachmi > > x50 - x200 faster. The set looks very interesting. I've had some ideas on how to speed up this part of configure already, so I'm doubly happy to see some work done in that area. At a first glance these

[libav-devel] [PATCH 1/3] configure: speed up flatten_extralibs_wrapper()

2018-09-16 Thread James Almer
From: Avi Halachmi x50 - x200 faster. Currently configure spends 50-70% of its runtime inside a single function: flatten_extralibs[_wrapper] - which does string processing. During its run, nearly 20K command substitutions (subshells) are used, including its callees unique() and resolve(),