1. 17 Jul, 2015 7 commits
  2. 16 Jul, 2015 25 commits
  3. 15 Jul, 2015 8 commits
    • caitpotter88's avatar
      [cleanup] remove --harmony-classes flag from mjsunit/harmony/new-target · 124d2011
      caitpotter88 authored
      Unknown flag warning is adding unnecessary noise to terminal during
      test runs
      
      BUG=
      LOG=N
      R=adamk@chromium.org
      
      Review URL: https://codereview.chromium.org/1236993003
      
      Cr-Commit-Position: refs/heads/master@{#29691}
      124d2011
    • adamk's avatar
      [api] Deprecate unused Map/Set FromArray factory methods · 9aa1dac8
      adamk authored
      These were added when I thought they would be useful in Blink, but as
      it turned out they were not. They could likely be deleted immediately,
      but to play it safe I'll go through the usual deprecation process.
      
      Review URL: https://codereview.chromium.org/1236263004
      
      Cr-Commit-Position: refs/heads/master@{#29690}
      9aa1dac8
    • bbudge's avatar
      Expose SIMD.Float32x4 type to Javascript. · e5ed3bee
      bbudge authored
      This CL exposes the constructor function, defines type related
      information, and implements value type semantics.
      It also refactors test/mjsunit/samevalue.js to test SameValue and SameValueZero.
      
      TEST=test/mjsunit/harmony/simd.js, test/cctest/test-simd.cc
      
      LOG=Y
      BUG=v8:4124
      
      Review URL: https://codereview.chromium.org/1219943002
      
      Cr-Commit-Position: refs/heads/master@{#29689}
      e5ed3bee
    • balazs.kilvady's avatar
      MIPS: Fix 'Reland Update V8 DEPS.' · bb247d4f
      balazs.kilvady authored
      Port c63e50ed
      
      BUG=
      TEST=test-disasm-mips/Type
      
      Review URL: https://codereview.chromium.org/1233323002
      
      Cr-Commit-Position: refs/heads/master@{#29688}
      bb247d4f
    • brucedawson's avatar
      Fix runtime-atomics for Win 10 SDK and remove volatile · b2ed2530
      brucedawson authored
      For unclear and probably accidental reasons the Windows 10 SDK
      renamed some _Interlocked* functions to _InlineInterlocked. This
      leads to these errors:
      
      runtime-atomics.cc(159): error C3861: '_InterlockedExchange64': identifier not found
      runtime-atomics.cc(159): error C3861: '_InterlockedExchangeAdd64': identifier not found
      runtime-atomics.cc(159): error C3861: '_InterlockedAnd64': identifier not found
      runtime-atomics.cc(159): error C3861: '_InterlockedOr64': identifier not found
      runtime-atomics.cc(159): error C3861: '_InterlockedXor64': identifier not found
      
      Fixing this requires either adding defines to map these five _Interlocked*
      functions to _InlineInterlocked*, or else changing to using the
      non-underscore versions. It appears that using the non-underscore versions
      is preferable so I went that way. This also requires adding three  new
      defines because there is a huge lack of consistency, probably due to these
      macros being defined sometimes in <intrin.h> and sometimes in <winnt.h>
      
      All five of the renamed 64-bit functions were manually checked to ensure
      that the change to the non-underscore versions would make no differences -
      the inline functions that they map to were identical. Other functions were
      spot-checked.
      
      Also, the 'volatile' qualifiers were removed. Volatile has no no useful
      meaning for multi-threaded programming. It only exists in the Interlocked*
      prototypes to *allow* volatile variables to be passed. Since this is a bad
      habit to encourage there is no reason for us to permit it, and we can
      still call the Microsoft functions (T* converts to volatile T*, just not
      vice-versa).
      
      The updated code builds with the Windows 8.1 SDK and with the Windows 10 SDK.
      
      R=jarin@chromium.org
      LOG=Y
      BUG=440500,491424
      
      Review URL: https://codereview.chromium.org/1228063005
      
      Cr-Commit-Position: refs/heads/master@{#29687}
      b2ed2530
    • verwaest's avatar
      Cleanup element normalization logic · 99b59d16
      verwaest authored
      BUG=
      
      Review URL: https://codereview.chromium.org/1241883002
      
      Cr-Commit-Position: refs/heads/master@{#29686}
      99b59d16
    • jkummerow's avatar
      Fix performance regression introduced in r29558 · 597af292
      jkummerow authored
      where bound functions started overriding the "name" accessor property with a data property. The bootstrapper must be kept in sync to avoid polymorphism.
      
      BUG=chromium:509983
      LOG=n
      R=verwaest@chromium.org
      
      Review URL: https://codereview.chromium.org/1238903002
      
      Cr-Commit-Position: refs/heads/master@{#29685}
      597af292
    • adamk's avatar
      Fix spread array inside array literal · 24e98281
      adamk authored
      During parsing, we now keep track of the first spread seen in an array
      literal (if any), and make use of that information when creating the
      FixedArray backing store representing the constant elements for array
      literal materialization.
      
      The old code tried to do this by setting the generated JSArray's length
      in ArrayLiteral::BuildConstantElements(), but that Array length is never
      read by the rest of the literal materialization code (it always uses
      the length of the FixedArray backing store).
      
      BUG=v8:4298
      LOG=n
      
      Review URL: https://codereview.chromium.org/1225223004
      
      Cr-Commit-Position: refs/heads/master@{#29684}
      24e98281