You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 5909932 I have replaced on Double::NewCanonical with Double::New(..., Heap::kOld) in the compiler.
This caused completely unexpected timeouts on Flutter tests internally. I added some time measurement around Double::New(..., Heap::kOld) and printed verbose timings for GC.
* when building IL from Kernel use canonical double representation
instead of allocating new double objects;
* in constant propagation canonicalize immutable primitive constants
(strings, mints and doubles) before replacing instruction with its
constant value;
This relands 5909932 with the part
that was causing timeouts on flutter_test reverted.
See #32904 for more details.
TBR=aam@google.com
Change-Id: I0c128e44dd6c9689c4b7e9dd91832408214847f3
Reviewed-on: https://dart-review.googlesource.com/51460
Reviewed-by: Vyacheslav Egorov <vegorov@google.com>
Reviewed-by: Alexander Aprelev <aam@google.com>
Commit-Queue: Vyacheslav Egorov <vegorov@google.com>
In 5909932 I have replaced on
Double::NewCanonical
withDouble::New(..., Heap::kOld)
in the compiler.This caused completely unexpected timeouts on Flutter tests internally. I added some time measurement around
Double::New(..., Heap::kOld)
and printed verbose timings for GC.Here is what I got:
These timings are very concerning: there are moments where VM takes 3 seconds to safepoint for GC and root marking times are measured in seconds.
/cc @a-siva @ErikCorryGoogle @rmacnak-google @mkustermann
The text was updated successfully, but these errors were encountered: