• Leszek Swirski's avatar
    [string] Fix casting around external internalized string thinning · 185389fa
    Leszek Swirski authored
    When an external string matches and internalized external string, we
    want to deduplicate them. As part of that de-duplication, we check if
    either a) the internalized string's resource is null (it's freshly
    created because the original string was in new space) or b) they point
    to the same data (in which case we don't want to dispose of the data).
    
    However, when doing these checks we cast both the initial and the
    internalized external string to the same type (one or two byte). So,
    if a two-byte string finds a one-byte internalized string with
    equivalent data, this cast will fail.
    
    Since we only care about the external string resource being null or
    equal to another during the above deduplication, the solution is
    casting first to the more general ExternalString type, comparing
    resources by address, and only casting to the more specific type
    when needed (and we know that the types have to match by other
    construction).
    
    Change-Id: Id34a02eb1900d8aa492c030488afaffd0d035454
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2315987
    Commit-Queue: Leszek Swirski <leszeks@chromium.org>
    Commit-Queue: Igor Sheludko <ishell@chromium.org>
    Auto-Submit: Leszek Swirski <leszeks@chromium.org>
    Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#69024}
    185389fa
string.cc 57.5 KB