Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index



On Tue, 2011-04-05 at 09:33 +0200, Bjoern Michaelsen wrote:
I did some rough measurements and they seem to make no noticeable
difference on a full build. They will however make a noticeable
different on a partial rebuild because it greatly reduces parsing the
huge dep files.

        Sure - I expect this only to impact the incremental make. Running 'make
-d -r' shows the reading to be the pain:

Reading makefile
`/data/opt/libreoffice/bootstrap/solver/300/unxlngi6.pro/workdir/Dep/LinkTarget/Library/libswdli.so.d'
 (search path) (no ~ expansion)...

        took ~1.5 seconds :-) it is 50Mb small:

ls -lh libswli.so.d 
-rw-r--r-- 1 michael users 50M Apr  4 18:31 libswli.so.d
wc -l libswli.so.d 
537483 libswli.so.d

        It seems to me that the fundamental problem is one of flattening all
dependencies of a file into a list; when in reality each file includes
only a dozen other files, which in turn include half a dozen, that in
turn ...

        In theory, make should be able to cope with some compressed /
intermediate representation of that (surely?).

        I wonder - if we had a single phony target for each file's
dependencies, and a tree of these, instead of this 50Mb flattened
monster blob; if that would be significantly faster [ and/or if it is
even possible ]

        Hmm,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.