On Thu, 2011-10-06 at 04:13 -0500, Norbert Thiebaud wrote:
One thing I noticed. It might be useful to run tinderboxes without gcc
optimization (ie. with -O0). It makes huge difference in compile time -
more than 10 times faster on my system and could make the tinderbox
turnaround much faster.
Yes, but the generated daily build would be less usefull that way and
possibly hide optimisation-induced bug until the last minute.
I thought the point of tinderboxes was to check quickly whether the tree
is buildable and report failure if not. I would consider differences
between whether an optimized or a non-optimized compilation would
complete to be compiler bug and ignore these. IMO, I would prefer
quicker turnarounds. Even more when the turnaround can be in order of 10
hours.
OTOH, we would need first to see how much would -O0 save for the whole
build.
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.