16abff0f85
The static min and max moments of QDateTimeParser are local times. Now that baseDate() needs to check whether the start of the two-year century falls between these, and parsing of simply a date or simply a time (not a date-time) uses UTC, to comparisons involve mapping the local time to UTC, with the usual associated expense. Do that expensive operation once on creation of the min and max local times, so that it'll be cached for use by the comparisons. This shall also help with other comparisons to max and min, so is of use even before the introduction of baseDate(), for all that that change brought the issue to light. Thanks to Jøger Hansegård for analysis of the profiler data that revealed the root cause of a significant slow-down. Pick-to: 6.7 6.5 Fixes: QTBUG-124465 Change-Id: I539c8ae782717635fb722c4573d85bc63073958a Reviewed-by: Jøger Hansegård <joger.hansegard@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit b6a11a4ee5319366f14c11c7cf3a4f1dbf33cfd5) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>