Revision: 2590
Author: [email protected]
Date: Thu Jul 30 07:18:09 2009
Log: Prepare push to trunk. We are now working towards version 1.3.2.
Review URL: http://codereview.chromium.org/160391
http://code.google.com/p/v8/source/detail?r=2590

Modified:
  /branches/bleeding_edge/ChangeLog
  /branches/bleeding_edge/src/version.cc

=======================================
--- /branches/bleeding_edge/ChangeLog   Mon Jul 27 01:27:28 2009
+++ /branches/bleeding_edge/ChangeLog   Thu Jul 30 07:18:09 2009
@@ -1,3 +1,25 @@
+2009-07-30: Version 1.3.1
+
+        Speed improvements to accessors and interceptors.
+
+        Added support for capturing stack information on custom errors.
+
+        Added support for morphing an object into a pixel array where its
+        indexed properties are stored in an external byte array. Values  
written
+        are always clamped to the 0..255 interval.
+
+        Profiler on x64 now handles C/C++ functions from shared libraries.
+
+        Changed the debugger to avoid stepping into function.call/apply if  
the
+        function is a built-in.
+
+        Initial implementation of constructor heap profile for JS objects.
+
+        More fine grained control of profiling aspects through the API.
+
+        Optimized the called as constructor check for API calls.
+
+
  2009-07-27: Version 1.3.0

          Allowed RegExp objects to be called as functions (issue 132).
=======================================
--- /branches/bleeding_edge/src/version.cc      Mon Jul 27 01:27:28 2009
+++ /branches/bleeding_edge/src/version.cc      Thu Jul 30 07:18:09 2009
@@ -34,7 +34,7 @@
  // cannot be changed without changing the SCons build script.
  #define MAJOR_VERSION     1
  #define MINOR_VERSION     3
-#define BUILD_NUMBER      1
+#define BUILD_NUMBER      2
  #define PATCH_LEVEL       0
  #define CANDIDATE_VERSION true


--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to