Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deps: backport rehash strings after deserialization #14345

Closed
wants to merge 1 commit into from

Commits on Jul 20, 2017

  1. deps: backport rehash strings after deserialization

    Original commit messages:
    v8/v8@a2ab135
      [snapshot] Rehash strings after deserialization.
    
      See https://goo.gl/6aN8xA
    
      Bug: v8:6593
      Change-Id: Ic8b0b57195d01d41591397d5d45de3f0f3ebc3d9
      Reviewed-on: https://chromium-review.googlesource.com/574527
      Reviewed-by: Camillo Bruni <cbruni@chromium.org>
      Reviewed-by: Jakob Gruber <jgruber@chromium.org>
      Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{nodejs#46732}
    
    v8/v8@182caaf
      Do not track transitions for built-in objects.
    
      Objects created during bootstrapping do not need
      a transition tree except for elements kind transitions.
    
      Bug: v8:6596
      Change-Id: I237b8b2792f201336e1c9731c815095dd06bc182
      Reviewed-on: https://chromium-review.googlesource.com/571750
      Reviewed-by: Igor Sheludko <ishell@chromium.org>
      Commit-Queue: Yang Guo <yangguo@chromium.org>
      Cr-Commit-Position: refs/heads/master@{nodejs#46693}
    
    Fixes: nodejs#14171
    PR-URL: nodejs#14345
    hashseed committed Jul 20, 2017
    Configuration menu
    Copy the full SHA
    404ade3 View commit details
    Browse the repository at this point in the history