Skip to content

V
V8
Switch branch/tag
  1. 29 Nov, 2016 1 commit
  3. 22 Nov, 2016 1 commit
  5. 25 Jul, 2016 1 commit
  7. 18 Jul, 2016 1 commit
  9. 17 Jun, 2016 1 commit
    • bmeurer's avatar
      [builtins] Introduce proper Float64Exp operator. · d5f2ac5e
      bmeurer authored 
      Import base::ieee754::exp() from FreeBSD msun and introduce a Float64Exp
TurboFan operator based on that, similar to what we do for Float64Log.
Rewrite Math.exp() as TurboFan builtin and use that operator to also
inline Math.exp() into optimized TurboFan functions.

CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:linux_chromium_rel_ng;tryserver.blink:linux_blink_rel
BUG=v8:3266,v8:3468,v8:3493,v8:5086,v8:5108,chromium:620786
R=mvstanton@chromium.org

Committed: https://crrev.com/93e26314afc9da9b5b8bd998688262444ed73260
Review-Url: https://codereview.chromium.org/2077533002
Cr-Original-Commit-Position: refs/heads/master@{#37037}
Cr-Commit-Position: refs/heads/master@{#37047}
      d5f2ac5e
  11. 16 Jun, 2016 2 commits
  13. 26 Apr, 2016 1 commit
  15. 08 Mar, 2016 1 commit
    • danno's avatar
      [runtime] Unify and simplify how frames are marked · 9dcd0857
      danno authored 
      Before this CL, various code stubs used different techniques
for marking their frames to enable stack-crawling and other
access to data in the frame. All of them were based on a abuse
of the "standard" frame representation, e.g. storing the a
context pointer immediately below the frame's fp, and a
function pointer after that. Although functional, this approach
tends to make stubs and builtins do an awkward, unnecessary
dance to appear like standard frames, even if they have
nothing to do with JavaScript execution.

This CL attempts to improve this by:

* Ensuring that there are only two fundamentally different
  types of frames, a "standard" frame and a "typed" frame.
  Standard frames, as before, contain both a context and
  function pointer. Typed frames contain only a minimum
  of a smi marker in the position immediately below the fp
  where the context is in standard frames.
* Only interpreted, full codegen, and optimized Crankshaft and
  TurboFan JavaScript frames use the "standard" format. All
  other frames use the type frame format with an explicit
  marker.
* Typed frames can contain one or more values below the
  type marker. There is new magic macro machinery in
  frames.h that simplifies defining the offsets of these fields
  in typed frames.
* A new flag in the CallDescriptor enables specifying whether
  a frame is a standard frame or a typed frame. Secondary
  register location spilling is now only enabled for standard
  frames.
* A zillion places in the code have been updated to deal with
  the fact that most code stubs and internal frames use the
  typed frame format. This includes changes in the
  deoptimizer, debugger, and liveedit.
* StandardFrameConstants::kMarkerOffset is deprecated,
  (CommonFrameConstants::kContextOrFrameTypeOffset
  and StandardFrameConstants::kFrameOffset are now used
  in its stead).

LOG=N

Review URL: https://codereview.chromium.org/1696043002

Cr-Commit-Position: refs/heads/master@{#34571}
      9dcd0857
  17. 19 Jan, 2016 1 commit
  19. 27 Nov, 2015 1 commit
  21. 26 Nov, 2015 1 commit
  23. 25 Nov, 2015 4 commits
  25. 24 Nov, 2015 1 commit
  27. 03 Sep, 2015 1 commit
  29. 17 Aug, 2015 1 commit
  31. 13 Jul, 2015 1 commit
  33. 01 Jun, 2015 1 commit
  35. 30 Jan, 2015 1 commit
  37. 22 Jan, 2015 2 commits
  39. 03 Dec, 2014 1 commit
  41. 09 Oct, 2014 1 commit
  43. 10 Sep, 2014 1 commit
  45. 12 Aug, 2014 1 commit
  47. 11 Aug, 2014 4 commits
  49. 06 Aug, 2014 1 commit
  51. 04 Aug, 2014 1 commit
  53. 15 Jul, 2014 2 commits
  55. 30 Jun, 2014 1 commit
  57. 03 Jun, 2014 1 commit
  59. 27 May, 2014 2 commits