1. 28 Jun, 2016 1 commit
    • bmeurer's avatar
      [turbofan] Introduce simplified operator NumberAbs. · f50a601f
      bmeurer authored
      Add NumberAbs operator to implement an inline version of Math.abs, that
      can be optimized and eliminated. We don't use any speculation here, but
      for now stick to the information we can infer (this way we avoid the
      inherent deopt loops that Crankshaft has around Math.abs).
      
      CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
      R=jarin@chromium.org
      BUG=v8:5086
      
      Review-Url: https://codereview.chromium.org/2096403002
      Cr-Commit-Position: refs/heads/master@{#37306}
      f50a601f
  2. 20 Jun, 2016 1 commit
  3. 19 Jun, 2016 1 commit
  4. 01 Apr, 2016 1 commit
  5. 08 Feb, 2016 1 commit
  6. 30 Nov, 2015 1 commit
    • bradnelson's avatar
      Make typing-asm match spec more closely around load/store, add more tests. · cf5546ba
      bradnelson authored
      Shifts of integer values are in some contexts collapsed by the parser into single literal AST nodes, rather than a direct representation of the parse tree. Confirming this behavior in tests.
      
      Integer TypedArrays are assumed to load and store "intish" values rather than more fine-grained type information. Reducing the precision of the typing information to match the spec and simplify the wasm generator.
      
      The asm spec requires load and store values of various "float?", "floatish", "double?" and "intish" types to ensure undefined values are not visible and that float32 rounding occurs at the right time. More closely matching this.
      
      Adding additional testing around unsigned / signed comparisons, loads and stores.
      
      Adding addition debug mode printing when asserting about types fail.
      
      BUG= https://code.google.com/p/v8/issues/detail?id=4203
      TEST=test-asm-validator, wasm side tests
      R=titzer@chromium.org,aseemgarg@chromium.org
      LOG=N
      
      Review URL: https://codereview.chromium.org/1471073003
      
      Cr-Commit-Position: refs/heads/master@{#32419}
      cf5546ba
  7. 26 Nov, 2015 1 commit
  8. 24 Nov, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Initial support for inline allocations of arrays. · e3905047
      bmeurer authored
      Add support for using inline allocations for arrays in lowering of
      JSCreateArray when target equals new.target.  Currently we are only
      concerend with the straight-forward Array() and Array(length) cases,
      but at some point TurboFan should also be able to support the more
      complex initializing cases.
      
      R=mvstanton@chromium.org
      BUG=v8:4470
      LOG=n
      
      Review URL: https://codereview.chromium.org/1465203002
      
      Cr-Commit-Position: refs/heads/master@{#32191}
      e3905047
  9. 17 Nov, 2015 1 commit
  10. 05 Nov, 2015 1 commit
  11. 04 Nov, 2015 1 commit
    • bmeurer's avatar
      [types] Use unified integral representation bits. · 6471fbf7
      bmeurer authored
      We don't need to distinguish between signed and unsigned integral
      representations in the big boy type system. It actually even hurts
      in some cases. The representation is only about the way the values
      are mapped to bits in memory/registers, but the interpretation of
      the bits is specified by the semantic dimension.
      
      R=jarin@chromium.org
      
      Review URL: https://codereview.chromium.org/1416953006
      
      Cr-Commit-Position: refs/heads/master@{#31771}
      6471fbf7
  12. 03 Nov, 2015 1 commit
  13. 29 Oct, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Initial support for transitioning stores. · a0b8650e
      bmeurer authored
      Add support for stores that transition to writable data fields,
      based on the BeginRegion/FinishRegion mechanism for atomic regions
      in the scheduler.
      
      This is early work and still a bit rough around the edges, and similar
      to regular stores, we don't support transitioning stores to double
      fields yet.
      
      R=jarin@chromium.org
      BUG=v8:4470
      LOG=n
      
      Review URL: https://codereview.chromium.org/1406153010
      
      Cr-Commit-Position: refs/heads/master@{#31645}
      a0b8650e
  14. 28 Oct, 2015 1 commit
  15. 26 Oct, 2015 1 commit
    • bmeurer's avatar
      [turbofan] Sanitize typing rules for function calls. · 3fbbfc38
      bmeurer authored
      Currently we (mostly) infer FunctionType for JSFunction constants, and
      match the FunctionType in the typing rule for JSCallFunction. This has
      several drawbacks for JavaScript, especially we don't have Constant
      types for global functions (i.e. String, Object, Reflect and friends).
      Plus the FunctionType magic doesn't actually buy us anything. So this
      changes the typing rule for HeapConstant constant to actually infer
      Constant types for JSFunction objects and moves the recognition of
      builtin functions to the typing rule for JSCallFunction.
      
      Also adapts the specialized lowering in JSTypedLowering to Constant
      functions instead of FunctionType, which has the additional advantage
      that we can do the receiver wrapping/converting based on the (known)
      SharedFunctionInfo.
      
      R=jarin@chromium.org
      
      Review URL: https://codereview.chromium.org/1420093005
      
      Cr-Commit-Position: refs/heads/master@{#31553}
      3fbbfc38
  16. 26 Aug, 2015 1 commit