libv8 5.2.361.43.1 → 5.3.332.38.0beta2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 43fd1487e4187e22711a0c704444c5a9ccf0234d
-  data.tar.gz: 4613f878a90eb8def2bbd281877ef734a0cfecfb
+  metadata.gz: a5f9904721cb788c2cf3da6f3424e1b78d4e6925
+  data.tar.gz: 47b9b3818f8d63c41817886545634287ac5b3bca
 SHA512:
-  metadata.gz: 70b10268110dac25734e44eee8f95fbb0a21d9b10de5af76ad35b1742e60287e252697409d9476baa37d6c81a59ee6775ad834fa154744b63bbcee04030a5c24
-  data.tar.gz: 1342f8040961ac0ff62e9b8f90805e576a0f71f81a7e70b5b774d510db90f137b8b244fb25b3133c83938e90abf52862881fbd0776c799245beaadfacf5458b8
+  metadata.gz: 2b650b61307b044fa5fa195fa87ccbbcf41477ebfd92bdcfc91d42445e97c6dd54a5f02049502e3325b1776302796c4355aba319de453132105a321d306661b6
+  data.tar.gz: 106f6c78794dced5caab933e5df6371391da190118af1b8e31b1bddf39a133c91a9ed618104d49830ee7aa97eb4fae15c87243494bc2f1b0ee9c48057e3696cf

data/.travis.yml

@@ -20,6 +20,7 @@ matrix:
     - rvm: 1.9.3
   allow_failures:
     - rvm: 1.9.3
+    - rvm: rbx
   fast_finish: true
 dist: trusty
 addons:

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+### Unreleased
+
+* Update upstream v8 version to 5.3.332.38
+
 ### 5.2.361.43.0, 5.2.361.43.1 - 2016-06-26:
 
 * Compare compiler versions part by part as integers instead of using string

data/README.md

@@ -2,6 +2,7 @@
 [![Gem Version](https://badge.fury.io/rb/libv8.svg)](http://badge.fury.io/rb/libv8)
 [![Build Status](https://travis-ci.org/cowboyd/libv8.svg?branch=master)](https://travis-ci.org/cowboyd/libv8)
 [![Join the chat at https://gitter.im/cowboyd/therubyracer](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/cowboyd/therubyracer?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+[![Code Triagers Badge](https://www.codetriage.com/cowboyd/libv8/badges/users.svg)](https://www.codetriage.com/cowboyd/libv8)
 
 A gem for distributing the v8 runtime libraries and headers in both
 source and binary form.

data/Rakefile

@@ -57,10 +57,10 @@ namespace :build do
       arch_dir = Pathname(__FILE__).dirname.join("release/#{arch}")
       Dir.chdir(arch_dir) do
         ENV['RUBYLIB'] = nil # https://github.com/mitchellh/vagrant/issues/6158
-        # sh "vagrant up"
-        # sh "vagrant ssh -c 'rm -rf ~/libv8'"
-        # sh "vagrant ssh -c 'git clone /libv8/.git ~/libv8 --recursive'"
-        # sh "vagrant ssh -c 'cd ~/libv8 && bundle install --path vendor/bundle'"
+        sh "vagrant up"
+        sh "vagrant ssh -c 'rm -rf ~/libv8'"
+        sh "vagrant ssh -c 'git clone /libv8/.git ~/libv8 --recursive'"
+        sh "vagrant ssh -c 'cd ~/libv8 && bundle install --path vendor/bundle'"
         sh "vagrant ssh -c 'cd ~/libv8 && MAKEFLAGS+=-j4 bundle exec rake binary'"
         sh "vagrant ssh -c 'cp ~/libv8/pkg/*.gem /vagrant'"
         sh "vagrant destroy"

data/ext/libv8/paths.rb

@@ -11,7 +11,7 @@ module Libv8
     end
 
     def object_paths
-      [:base, :libplatform, :libbase, :snapshot].map do |name|
+      [:base, :libplatform, :libsampler, :libbase, :snapshot].map do |name|
         Shellwords.escape libv8_object(name)
       end
     end

data/lib/libv8/version.rb

@@ -1,3 +1,3 @@
 module Libv8
-  VERSION = "5.2.361.43.1"
+  VERSION = "5.3.332.38.0beta2"
 end

data/libv8.gemspec

@@ -14,7 +14,7 @@ Gem::Specification.new do |s|
 
   s.rubyforge_project = "libv8"
 
-  s.files  = `git ls-files`.split("\n")
+  s.files  = `git ls-files`.split("\n").reject {|f| f =~ /^release\//}
 
   submodules = `git submodule --quiet foreach 'echo $path'`.split("\n").map(&:chomp)
   submodules.each do |submodule|

data/patches/0001-Build-a-standalone-static-library.patch

@@ -1,4 +1,4 @@
-From 84470a0b6c696f42aa7f86ba5ffd22b17e0047c4 Mon Sep 17 00:00:00 2001
+From 8e34b0f097ea5ea5bbde4ee8b7fd6521d40dd5e3 Mon Sep 17 00:00:00 2001
 From: Petko Bordjukov <bordjukov@gmail.com>
 Date: Mon, 25 Jul 2016 00:00:19 +0300
 Subject: [PATCH 1/4] Build a standalone static library
@@ -8,10 +8,10 @@ Subject: [PATCH 1/4] Build a standalone static library
  1 file changed, 3 insertions(+)
 
 diff --git a/gypfiles/standalone.gypi b/gypfiles/standalone.gypi
-index 630c45e..1a69c6f 100644
+index c6c26fb..a59e12b 100644
 --- a/gypfiles/standalone.gypi
 +++ b/gypfiles/standalone.gypi
-@@ -488,6 +488,9 @@
+@@ -505,6 +505,9 @@
        }],  # fastbuild!=0
      ],
      'target_conditions': [
@@ -22,5 +22,5 @@ index 630c45e..1a69c6f 100644
          'defines!': [
            'DEBUG',
 -- 
-2.9.0
+2.9.3
 

data/patches/0002-Don-t-compile-unnecessary-stuff.patch

@@ -1,4 +1,4 @@
-From 930d596106fb3289f6aa37cdf8abaec3106c31b9 Mon Sep 17 00:00:00 2001
+From 48d4b7ae6cbb8a2109555f57845fa5f6aa4fa30a Mon Sep 17 00:00:00 2001
 From: Petko Bordjukov <bordjukov@gmail.com>
 Date: Mon, 25 Jul 2016 00:04:07 +0300
 Subject: [PATCH 2/4] Don't compile unnecessary stuff
@@ -9,10 +9,10 @@ Subject: [PATCH 2/4] Don't compile unnecessary stuff
  2 files changed, 1 insertion(+), 38 deletions(-)
 
 diff --git a/Makefile b/Makefile
-index 0f8f93a..68778e9 100644
+index ffb5192..8e60aab 100644
 --- a/Makefile
 +++ b/Makefile
-@@ -264,12 +264,7 @@ GYPFILES = third_party/icu/icu.gypi third_party/icu/icu.gyp \
+@@ -265,12 +265,7 @@ GYPFILES = third_party/icu/icu.gypi third_party/icu/icu.gyp \
  	   gypfiles/shim_headers.gypi gypfiles/features.gypi \
             gypfiles/standalone.gypi \
  	   gypfiles/toolchain.gypi gypfiles/all.gyp gypfiles/mac/asan.gyp \
@@ -70,5 +70,5 @@ index ff1bea4..96820a0 100644
      }
    ]
 -- 
-2.9.0
+2.9.3
 

data/patches/0003-Use-the-fPIC-flag-for-the-static-library.patch

@@ -1,4 +1,4 @@
-From 8873d0ee6e1304e256bf3181b287e189bc68a9c8 Mon Sep 17 00:00:00 2001
+From 44da612b4aa078bc2090cad3bd42506f444dd900 Mon Sep 17 00:00:00 2001
 From: Petko Bordjukov <bordjukov@gmail.com>
 Date: Mon, 25 Jul 2016 00:05:47 +0300
 Subject: [PATCH 3/4] Use the -fPIC flag for the static library
@@ -8,10 +8,10 @@ Subject: [PATCH 3/4] Use the -fPIC flag for the static library
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/gypfiles/standalone.gypi b/gypfiles/standalone.gypi
-index 1a69c6f..b19304f 100644
+index a59e12b..4e64f2e 100644
 --- a/gypfiles/standalone.gypi
 +++ b/gypfiles/standalone.gypi
-@@ -744,7 +744,7 @@
+@@ -772,7 +772,7 @@
            [ 'visibility=="hidden" and v8_enable_backtrace==0', {
              'cflags': [ '-fvisibility=hidden' ],
            }],
@@ -21,5 +21,5 @@ index 1a69c6f..b19304f 100644
            }],
            [ 'clang==0 and coverage==1', {
 -- 
-2.9.0
+2.9.3
 

data/patches/0004-Reinterpret-thread-hash-for-FreeBSD-too.patch

@@ -1,17 +1,17 @@
-From 0f376ac8f77980b86bfbfb55e3a1714201a0f78f Mon Sep 17 00:00:00 2001
+From cf7ec827796ccaef75e77bd83771e7f31b645d2f Mon Sep 17 00:00:00 2001
 From: Petko Bordjukov <bordjukov@gmail.com>
 Date: Wed, 27 Jul 2016 06:20:13 +0300
 Subject: [PATCH 4/4] Reinterpret thread hash for FreeBSD, too
 
 ---
- src/profiler/sampler.cc | 2 +-
+ src/libsampler/v8-sampler.cc | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
-diff --git a/src/profiler/sampler.cc b/src/profiler/sampler.cc
-index ae47dca..4eb8780 100644
---- a/src/profiler/sampler.cc
-+++ b/src/profiler/sampler.cc
-@@ -210,7 +210,7 @@ void* ThreadKey(pthread_t thread_id) {
+diff --git a/src/libsampler/v8-sampler.cc b/src/libsampler/v8-sampler.cc
+index edf6df1..9b2a718 100644
+--- a/src/libsampler/v8-sampler.cc
++++ b/src/libsampler/v8-sampler.cc
+@@ -194,7 +194,7 @@ void* ThreadKey(pthread_t thread_id) {
  
  // Returns hash value for hash map.
  uint32_t ThreadHash(pthread_t thread_id) {
@@ -21,5 +21,5 @@ index ae47dca..4eb8780 100644
  #else
    return static_cast<uint32_t>(thread_id);
 -- 
-2.9.0
+2.9.3
 

data/spec/location_spec.rb

@@ -64,7 +64,7 @@ describe "libv8 locations" do
     end
 
     it "prepends the locations of any libv8 objects on the the ldflags" do
-      expect(@context.ldflags).to eql "/foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_base.a /foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_libplatform.a /foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_libbase.a /foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_snapshot.a -lobjc -lpthread"
+      expect(@context.ldflags).to eql "/foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_base.a /foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_libplatform.a /foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_libsampler.a /foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_libbase.a /foo\\ bar/v8/out/x64.release/obj.target/tools/gyp/libv8_snapshot.a -lobjc -lpthread"
     end
   end
 end

data/vendor/depot_tools/README.gclient.md

@@ -0,0 +1,67 @@
+# gclient
+
+gclient is a tool for managing a modular checkout of source code from multiple
+source code repositories. It wraps underlying source code management commands
+to provide support for distributing tree updates, status commands, and diffs
+across multiple checked-out working directories.
+
+The gclient script is controlled by a `.gclient` file at the top of a directory
+tree which will contain source code from multiple locations. A `.gclient` file
+is a Python script that defines a list of `solutions` with the following format:
+
+    solutions = [
+      { "name"        : "src",
+        "url"         : "svn://svnserver/component/trunk/src",
+        "custom_deps" : {
+          # To use the trunk of a component instead of what's in DEPS:
+          #"component": "https://svnserver/component/trunk/",
+          # To exclude a component from your working copy:
+          #"data/really_large_component": None,
+        }
+      },
+    ]
+
+A `solution` is a collection of component pieces of software that will be
+checked out in a specific directory layout for building together.
+
+Each entry in the `solutions` list is defined by a Python dictionary that
+contains the following items:
+
+- `name`: The name of the directory in which the solution will be checked out.
+- `url`: The URL from which this solution will be checked out. gclient expects
+  that the checked-out solution will contain a file named `DEPS` that in turn
+  defines the specific pieces that must be checked out to create the working
+  directory layout for building and developing the solution's software.
+- `deps_file`: A string containing just the filename (not a path) of the file in
+  the solution dir to use as the list of dependencies. This tag is optional, and
+  defaults to `DEPS`.
+- `custom_deps`: A dictionary containing optional custom overrides for entries
+  in the solution's `DEPS` file.  This can be used to have the local working
+  directory *not* check out and update specific components, or to sync the local
+  working-directory copy of a given component to a different specific revision,
+  or a branch, or the head of a tree. It can also be used to append new entries
+  that do not exist in the `DEPS` file.
+
+Within each checked-out solution, gclient expects to find a file typically named
+`DEPS` (it actually uses the value of the `deps_file` key above) which defines
+the different component pieces of software that must be checked out for the
+solution. The `DEPS` file is a Python script that defines a dictionary named
+`deps`:
+
+    deps = {
+      "src/outside": "https://outside-server/one/repo.git@12345677890123456778901234567789012345677890",
+      "src/component": "https://dont-use-github.com/its/unreliable.git@0000000000000000000000000000000000000000",
+      "src/relative": "/another/repo.git@aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
+    }
+
+Each item in the `deps` dictionary consists of a key-value pair. The key is the
+directory into which the component will be checked out, relative to the
+directory containing the `.gclient` file. The value is the URL from which that
+directory will be checked out. If there is no address scheme (that is, no
+`http:` or `svn:` prefix), then the value must begin with a slash and is treated
+relative to the root of the solution's repository.
+
+The URL typically contains a specific revision or change number (as appropriate
+for the underlying SCM system) to `freeze` the external software at a specific,
+known state. Alternatively, if there is no revision or change number, the URL
+will track the latest changes on the specific trunk or branch.

data/vendor/depot_tools/README.git-cl.md

@@ -0,0 +1,112 @@
+# git-cl
+
+The git-cl README describes the git-cl command set. This document describes how
+code review and git work together in general, intended for people familiar with
+git but unfamiliar with the code review process supported by Rietveld and
+Gerrit.
+
+
+## Reitveld concepts and terms
+
+A Rietveld review is for discussion of a single change or patch. You upload a
+proposed change, the reviewer comments on your change, and then you can upload a
+revised version of your change. Rietveld stores the history of uploaded patches
+as well as the comments, and can compute diffs in between these patches. The
+history of a patch is very much like a small branch in git, but since Rietveld
+is VCS-agnostic the concepts don't map perfectly. The identifier for a single
+review+patches+comments in Rietveld is called an `issue`.
+
+Rietveld provides a basic uploader that understands git. This program is used by
+git-cl, and is included in the git-cl repo as upload.py.
+
+
+## Basic interaction with git
+
+The fundamental problem you encounter when you try to mix git and code review is
+that with git it's nice to commit code locally, while during a code review
+you're often requested to change something about your code. There are a few
+different ways you can handle this workflow with git:
+
+1. Rewriting a single commit. Say the origin commit is O, and you commit your
+   initial work in a commit A, making your history like O--A. After review
+   comments, you commit --amend, effectively erasing A and making a new commit
+   A', so history is now O--A'. (Equivalently, you can use git reset --soft or
+   git rebase -i.)
+2. Writing follow-up commits. Initial work is again in A, and after review
+   comments, you write a new commit B so your history looks like O--A--B. When
+   you upload the revised patch, you upload the diff of O..B, not A..B; you
+   always upload the full diff of what you're proposing to change.
+
+The Rietveld patch uploader just takes arguments to `git diff`, so either of the
+above workflows work fine.  If all you want to do is upload a patch, you can use
+the upload.py provided by Rietveld with arguments like this:
+
+    upload.py --server server.com <args to "git diff">
+
+The first time you upload, it creates a new issue; for follow-ups on the same
+issue, you need to provide the issue number:
+
+    upload.py --server server.com --issue 1234 <args to "git diff">
+
+
+## git-cl to the rescue
+
+git-cl simplifies the above in the following ways:
+
+1. `git cl config` puts a persistent --server setting in your .git/config.
+2. The first time you upload an issue, the issue number is associated with the
+   current *branch*.  If you upload again, it will upload on the same issue.
+   (Note that this association is tied to a branch, not a commit, which means
+   you need a separate branch per review.)
+3. If your branch is _tracking_ (in the `git checkout --track` sense) another
+   one (like origin/master), calls to `git cl upload` will diff against that
+   branch by default.  (You can still pass arguments to `git diff` on the
+   command line, if necessary.)
+
+In the common case, this means that calling simply `git cl upload` will always
+upload the correct diff to the correct place.
+
+
+## Patch series
+
+The above is all you need to know for working on a single patch.
+
+Things get much more complicated when you have a series of commits that you want
+to get reviewed. Say your history looks like O--A--B--C. If you want to upload
+that as a single review, everything works just as above.
+
+But what if you upload each of A, B, and C as separate reviews? What if you
+then need to change A?
+
+1. One option is rewriting history: write a new commit A', then use git rebase
+   -i to insert that diff in as O--A--A'--B--C as well as squash it. This is
+   sometimes not possible if B and C have touched some lines affected by A'.
+2. Another option, and the one espoused by software like topgit, is for you to
+   have separate branches for A, B, and C, and after writing A' you merge it
+   into each of those branches. (topgit automates this merging process.)  This
+   is also what is recommended by git-cl, which likes having different branch
+   identifiers to hang the issue number off of.  Your history ends up looking
+   like:
+
+       O---A---B---C
+            \   \   \
+             A'--B'--C'
+
+   Which is ugly, but it accurately tracks the real history of your work, can be
+   thrown away at the end by committing A+A' as a single `squash` commit.
+
+In practice, this comes up pretty rarely. Suggestions for better workflows are
+welcome.
+
+## Bash auto complition
+
+1. Ensure that your base git commands are autocompleted
+[doc](https://git-scm.com/book/en/v1/Git-Basics-Tips-and-Tricks).
+2. Add this to your .bashrc:
+    
+        # The next line enables bash completion for git cl.
+        if [ -f "$HOME/bin/depot_tools/git_cl_completion.sh" ]; then
+          . "$HOME/bin/depot_tools/git_cl_completion.sh"
+        fi
+        
+3. Profit.

data/vendor/depot_tools/README.md

@@ -1,55 +1,69 @@
-This package contains tools for working with Chromium development:
+# depot_tools
 
-  chrome-update-create-task.bat
-    Creates a scheduled task to do an automatic local chromium build every day.
+This package contains tools for working with Chromium development. It requires
+python 2.7.
 
-  cpplint.py
-    A copy of our linting tool which enforces Google style. Fetched from
-    http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py
 
-  gcl
-    A tool for uploading and managing code reviews on the Chromium
-    project, using the Rietveld code review tool.  More info at:
-    http://code.google.com/p/rietveld/
+## Tools
 
-  gclient
-    A script for managing a workspace with modular dependencies that
-    are each checked out independently from different repositories.
-    More info at:
-    http://code.google.com/p/gclient/
+The most important tools are:
 
-It updates itself automatically when running `gclient` tool. To disable
-auto update, set the environment variable DEPOT_TOOLS_UPDATE=0
+- `fetch`: A `gclient` wrapper to checkout a project. Use `fetch --help` for
+  more details.
+- `gclient`: A meta-checkout tool. Think
+  [repo](https://source.android.com/source/using-repo.html) or [git
+  submodules](https://git-scm.com/docs/git-submodule), except that it support
+  OS-specific rules, e.g. do not checkout Windows only dependencies when
+  checking out for Android. Use `gclient help` for more details and
+  [README.gclient.md](README.gclient.md).
+- `git cl`: A code review tool to interact with Rietveld or Gerrit. Use `git cl
+  help` for more details and [README.git-cl.md](README.git-cl.md).
+- `roll-dep`: A gclient dependency management tool to submit a _dep roll_,
+  updating a dependency to a newer revision.
 
-To update package manually, run .\update_depot_tools.bat on Windows,
-or ./update_depot_tools on Linux or Mac.
+There are a lot of git utilities included.
 
-Note: on Windows if svn, git and python are not accessible, they will be
-downloaded too.
 
+## Updating
 
-## Contributing
+`depot_tools` updates itself automatically when running `gclient` tool. To
+disable auto update, set the environment variable `DEPOT_TOOLS_UPDATE=0`.
+
+To update package manually, run `update_depot_tools.bat` on Windows,
+or `./update_depot_tools` on Linux or Mac.
+
+On Windows only, running `gclient` will install `svn` (not for long), `git`,
+`python`.
 
-The "gclient" wrapper knows how to keep this repository updated to
-the latest versions of these tools as found at:
 
-    https://chromium.googlesource.com/chromium/tools/depot_tools.git
+## Contributing
 
 To contribute change for review:
 
     git new-branch <somename>
-    git add <yourchanges>
-    git commit
+    # Hack
+    git add .
+    git commit -a -m "Fixes goat teleporting"
     # find reviewers
     git cl owners
-    git log <yourfiles>
-    # upload
-    git cl upload -r reviewer1@chromium.org,reviewer2 --send-mail
-    # open https://codereview.chromium.org/ and send mail
-
-    # if change is approved, flag it to be commited
-    git cl set_commit
-    # if change needs more work
+    git log -- <yourfiles>
+
+    # Request a review.
+    git cl upload -r reviewer1@chromium.org,reviewer2@chromium.org --send-mail
+
+    # Edit change description if needed.
+    git cl desc
+
+    # If change is approved, flag it to be commited.
+    git cl set-commit
+
+    # If change needs more work.
     git rebase-update
     ...
-    git cl upload
+    git cl upload -t "Fixes goat teleporter destination to be Australia"
+
+
+### cpplint.py
+
+To update cpplint.py, please submit the change upstream first at
+https://github.com/google/styleguide/tree/gh-pages/cpplint then copy it down.