1. 02 Mar, 2010 1 commit
  2. 04 Feb, 2010 2 commits
  3. 05 Nov, 2009 1 commit
  4. 04 Nov, 2009 1 commit
  5. 29 Oct, 2009 1 commit
  6. 27 Oct, 2009 1 commit
  7. 26 Oct, 2009 2 commits
  8. 08 Oct, 2009 1 commit
  9. 16 Sep, 2009 1 commit
    • mikhail.naganov@gmail.com's avatar
      Add initial version of retainers heap profile. · abc0bd46
      mikhail.naganov@gmail.com authored
      The profile is taken together with constructors profile. In theory, it
      should represent a complete heap graph. However, this takes a lot of memory,
      so it is reduced to a more compact, but still useful form. Namely:
      
       - objects are aggregated by their constructors, except for Array and Object
         instances, that are too hetereogeneous;
      
       - for Arrays and Objects, initially every instance is concerned, but then
         they are grouped together based on their retainer graph paths similarity (e.g.
         if two objects has the same retainer, they are considered equal);
      
      Review URL: http://codereview.chromium.org/200132
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2903 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      abc0bd46
  10. 19 Aug, 2009 1 commit
  11. 31 Jul, 2009 1 commit
  12. 28 May, 2009 1 commit
    • mikhail.naganov@gmail.com's avatar
      Implement a dynamically growing memory log buffer with an upper limit. · e48095b8
      mikhail.naganov@gmail.com authored
      The goal of this change is to allow longer profiling sessions and preserve memory when profiler isn't started. The buffer starts with 64K and grows until it reaches the upper limit, which is currently set to 50MB --- according to my evaluations, this is enough for at least 20 minutes of GMail profiling. As we're planning to introduce compression for the profiler log, this time boundary will be significantly increased soon.
      
      To make possible unit testing of the new component, I've factored out Logger's utility classes into a separate source file: log-utils.h/cc. Log and LogMessageBuilder are moved there from log.cc without any semantical changes.
      
      Review URL: http://codereview.chromium.org/115814
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2067 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      e48095b8
  13. 26 May, 2009 1 commit
  14. 05 May, 2009 1 commit
  15. 30 Apr, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Added better version information · a4708472
      sgjesse@chromium.org authored
      The current version is now held in src/version.cc in a number of defines which needs to be modified when changing version.
      
      The following defines make up the version information:
      
        MAJOR_VERSION
        MINOR_VERSION
        BUILD_NUMBER
        PATCH_LEVEL
        CANDIDATE_VERSION
      
      The first four are numbers and the fifth is a boolean. Besides these five the define
      
        SONAME
      
      can be used to set a specific soname when building the a shared library (see below). This will most likely be used on stable branches where binary compatibility is ensured between different versions. This define is a string.
      
      This version information is now read by the SCons build to support setting the soname for a Linux shared library. This requires passing the option soname=on to the SCons build.
      
      When soname=on is specified the soname for the shared library can be set in two different ways. Either it will be the full versioned library name (e.g. libv8-1.2.2.so) or a specific soname defined in src/version.cc. Whenever a shared library is build with an soname the filename of the library will hold the full version name (e.g. libv8-1.2.2.so).
      
      I did not update the xcode project with the new files.
      
      BUG=151
      Review URL: http://codereview.chromium.org/100104
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1826 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      a4708472
  16. 14 Apr, 2009 1 commit
  17. 05 Mar, 2009 1 commit
  18. 25 Feb, 2009 1 commit
  19. 24 Feb, 2009 1 commit
    • sgjesse@chromium.org's avatar
      Add socket support to platform code. · be059966
      sgjesse@chromium.org authored
      The new Socket class is an encapsulation of the standard BSD socket API. As it depends on platform specific include files and have some slight platform variations it is part of the platform code.
      
      On Mac OS only the option SO_REUSEADDR is set to true for server sockets. Running the test required it as the bound listener socket would sometimes end up in TIME_WAIT. On Windows and Linux this has never been observed (given the client end of the socket is closed before the server end).
      
      The code has been tested on Windows, Linux and Mac OS. The FreeBSD version is a copy of the Linux version but has not been compiled nor tested.
      
      Missing Xcode project updates.
      Review URL: http://codereview.chromium.org/27085
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1349 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      be059966
  20. 17 Dec, 2008 1 commit
  21. 25 Nov, 2008 1 commit
  22. 30 Oct, 2008 1 commit
  23. 09 Sep, 2008 1 commit
  24. 05 Sep, 2008 1 commit
  25. 02 Sep, 2008 1 commit
  26. 22 Aug, 2008 1 commit
    • christian.plesner.hansen's avatar
      Included mjsunit JavaScript test suite and C++ unit tests. · c42f5829
      christian.plesner.hansen authored
      In the shell sample don't print the result of executing a script, only
      evaluating expressions.
      
      Fixed issue when building samples on Windows using a shared V8
      library.  Added visibility option on Linux build which makes the
      generated library 18% smaller.
      
      Changed build system to accept multiple build modes in one build and
      generate seperate objects, libraries and executables for each mode.
      
      Removed deferred negation optimization (a * -b => -(a * b)) since this
      visibly changes operand conversion order.
      
      Improved parsing performance by introducing stack guard in preparsing.
      Without a stack guard preparsing always bails out with stack overflow.
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c42f5829