• Mythri A's avatar
    [turboprop] Don't consider stores to constant fields as mutable · b9a59e38
    Mythri A authored
    Turboprop doesn't use optimizations based on field constness to reduce
    the number of deoptimizations. While this is safe for loads, for stores
    if a different value is stored to a const field we should update the
    constness of the field. This is needed so we can safely deopt any other
    code that is relying on the constness of the field. Currently, turboprop
    doesn't do this. So for now treat stores to constant fields similar to
    TurboFan. In future, we may consider adding code to update the field
    constness if necessary to reduce the number of deoptimizations.
    
    
    Bug: chromium:1172797, v8:9684
    Change-Id: I1d660457cb5d647e1283a495040a7e452fe1ac7e
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2673401
    Commit-Queue: Mythri Alle <mythria@chromium.org>
    Reviewed-by: 's avatarGeorg Neis <neis@chromium.org>
    Reviewed-by: 's avatarSathya Gunasekaran  <gsathya@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#72590}
    b9a59e38
access-info.cc 36.9 KB