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


On 05.11.2012 17:15, Michael Meeks wrote:
        Why do I extensively use that option, though I'm not a packager:

        * I like to run the code the end-user runs - warts and all.
        * I like to be able to profile accurately without re-building
          everything (cf. above)
        * Having no symbols / debug-info is rather unhelpful for both
          debugging, and profiling though  perhaps it's a reasonable
          default for size reasons

On 05.11.2012 18:06, Norbert Thiebaud wrote:
actually that is platform and even sometime source dependent.
which makes global level carpet bombing using CFLAGS/CXXFLAGS/LDFLAGS
a not necessarily appealing option.

Thank you both for this justfication,
which i've shamelsellsy stolen for the commit message ;-)

On 05.11.2012 18:10, Michael Stahl wrote:
Note that what the end user runs is -O2 rather than -Os IIUC.
yes...and no. both are true actually:

>[0] ms@bastet:/master > git grep -- "-O2" solenv/gbuild/  | wc -l
>18
>[0] ms@bastet:/master > git grep -- "-Os" solenv/gbuild/  | wc -l
>10
>[0] ms@bastet:/master > git grep -- "-O " solenv/gbuild/platform/  | wc -l
>2
so if you want to do profiling you simply have to look up which one your
particular architecture uses first to get meaningful numbers.
No you shouldn't! That what the build systems are for:

https://gerrit.libreoffice.org/#/c/975/

Regards
David

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.