- 12 Mar, 2012 7 commits
-
-
erik.corry@gmail.com authored
Review URL: https://chromiumcodereview.appspot.com/9600009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11007 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=svenpanne@chromium.org Review URL: https://chromiumcodereview.appspot.com/9662056 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11006 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
This is necessary in order to link v8_shell (for host) with the Android toolchain. Without it, the line in the makefile is: $(builddir)/v8_shell: LD_INPUTS := $(OBJS) $(obj).host/v8/tools/gyp/libv8_snapshot.a $(obj).host/v8/tools/gyp/libv8_base.a Now it appears as: $(builddir)/v8_shell: LD_INPUTS := $(OBJS) $(obj).host/v8/tools/gyp/libv8_base.a $(obj).host/v8/tools/gyp/libv8_snapshot.a and it successfully links. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9668013 Patch from Yaron Friedman <yfriedman@chromium.org>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11005 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
This changes the heuristic that starts incremental marking to be based on a more accurate heap size estimation. Pages being swept lazily can be accounted using the live bytes counter. R=mstarzinger@chromium.org BUG=v8:1682 Review URL: https://chromiumcodereview.appspot.com/9674001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11004 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ulan@chromium.org authored
Port r10981 (5ea074), r10982 (5f0d413) and r10983 (663a897d5). BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9668045 Patch from Daniel Kalmar <kalmard@homejinni.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11003 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
Port r10988 (c6c9ebb5). Original commit message: Inline inequality compares of strings into CompareICStub instead of jumping into the CompareStub that handles the generic case. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9669026 Patch from Daniel Kalmar <kalmard@homejinni.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@11002 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
R=jkummerow@chromium.org BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9690004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10999 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 11 Mar, 2012 5 commits
-
-
loislo@chromium.org authored
BUG=none TEST=profile-generator tests Review URL: https://chromiumcodereview.appspot.com/9632020 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10998 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
loislo@chromium.org authored
BUG=none TEST=none TBR=mikhail.naganov@gmail.com Review URL: https://chromiumcodereview.appspot.com/9664042 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10997 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
loislo@chromium.org authored
We have a problem with really big apps. The snapshot for such pages doesn't fit into JS heap on DevTools front-end side. I'd like to move the snapshot's nodes data into Int32Array. This will reduce the pressure. At this moment it is not possible because the snapshot uses uint64_t for ids. BUG=none TEST=profiler-generator tests Review URL: https://chromiumcodereview.appspot.com/9617006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10996 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
loislo@chromium.org authored
Revert "We have a problem with really big apps. The snapshot for such pages doesn't fit into JS heap on DevTools front-end side. I'd like to move the snapshot's nodes data into Int32Array." This reverts commit 8c08ecc2782d5a8c60eb0692ec8f13d6da3cdc58. BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/9666038 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10995 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
loislo@chromium.org authored
We have a problem with really big apps. The snapshot for such pages doesn't fit into JS heap on DevTools front-end side. I'd like to move the snapshot's nodes data into Int32Array. This will reduce the pressure. At this moment it is not possible because the snapshot uses uint64_t for ids. BUG=none TEST=profiler-generator tests Review URL: https://chromiumcodereview.appspot.com/9617006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10994 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 09 Mar, 2012 19 commits
-
-
yangguo@chromium.org authored
BUG=http://code.google.com/p/v8/issues/detail?id=1996 TEST=none Review URL: https://chromiumcodereview.appspot.com/9669003 Patch from Rodolph Perfetta <rodolph.perfetta@gmail.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10993 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
This doesn't enable the experimental profiler by default, it just tunes its behavior when it is enabled. Review URL: https://chromiumcodereview.appspot.com/9668009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10992 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/9633012 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10991 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
TBR=jkummerow@chromium.org Review URL: https://chromiumcodereview.appspot.com/9665002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10990 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/9638014 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10989 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
Inline inequality compares of strings into CompareICStub instead of jumping into the CompareStub that handles the generic case. BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9649027 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10988 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ulan@chromium.org authored
R=mstarzinger@chromium.org BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9652030 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10987 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vegorov@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/9361008 Patch from David Pacheco <dap@joyent.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10986 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vegorov@chromium.org authored
Port r10901 (a54f1a3). BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9586004 Patch from Daniel Kalmar <kalmard@homejinni.com>. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10985 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
R=mstarzinger@chromium.org BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9655025 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10984 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ulan@chromium.org authored
Developed together with Andreas Rossberg based on: https://chromiumcodereview.appspot.com/9117034/ https://chromiumcodereview.appspot.com/9307083/ R=rossberg@chromium.org Review URL: https://chromiumcodereview.appspot.com/9572008 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10983 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
This is based on https://chromiumcodereview.appspot.com/9117034/ Doesn't have much impact on its own, but is the basis for Ulan's CL https://chromiumcodereview.appspot.com/9117034/, which moves the logic to C++. R=ulan@chromium.org BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9307083 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10982 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
First step, cache slots not used yet. R=ulan@chromium.org BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9117034 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10981 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Review URL: https://chromiumcodereview.appspot.com/9652028 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10978 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
While enabling "-fstack-protector", compiler generates code in function prologue and epilogue to do stack check. However, without knowing that 'r1', 'r2' and 'r3' is used/destroyed in inline asm, compiler assumes that 'r1', 'r2', or 'r3' can be used exclusively, which leads to a core dump. Fix to this is quite straightforward, just add clobber list to the inlineasm. BUG=None TEST=manually checked the generated asm code,boot up chrome browser successfully with this modification Review URL: https://chromiumcodereview.appspot.com/9618017 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10977 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
Moved common code into tools/common-includes.sh. Added automated rolling of V8 into Chromium to push-to-trunk.sh. Review URL: https://chromiumcodereview.appspot.com/9463041 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10976 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9592047 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10975 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ulan@chromium.org authored
r10435 CL: http://codereview.chromium.org/9195005 r10923 CL: https://chromiumcodereview.appspot.com/9601010 R=fschneider@chromium.org Review URL: https://chromiumcodereview.appspot.com/9653025 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10974 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
This is a preparatory step for using the HashMap clas with Literal keys in the full code generator. It removes some duplicated code already and removes the need for 2 HashMaps at each use, which was overly complicated. Removed one dead function on the way. Review URL: https://chromiumcodereview.appspot.com/9639011 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10973 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 08 Mar, 2012 8 commits
-
-
mikhail.naganov@gmail.com authored
The patch is based on the report provided by github user Zakay. BUG=none TEST=none Review URL: https://chromiumcodereview.appspot.com/9592030 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10970 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
Rrraaa, I have to say, doing program rewriting via regexp rules is an inherently broken idea... R=mstarzinger@chromium.org BUG= TEST= Review URL: https://chromiumcodereview.appspot.com/9644001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10969 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
1. The write barrier (RecordWriteStub) expects that pointer stored points to an initialized object. Specifically, the map must be set before it is stored. 2. The backing store for smi-only elements can only be reused for double elements if it is in new-space. Otherwise, we need to allocate a fresh one because the old one is in pointer-space and the new one has to be in data-space. BUG=117037 Review URL: https://chromiumcodereview.appspot.com/9633017 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10968 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=rossberg@chromium.org TEST=mjsunit/object-is Review URL: https://chromiumcodereview.appspot.com/9641015 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10967 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
All module expressions, and all variables that might refer to modules, are assigned interfaces (module types) that are resolved using unification. This is necessary to deal with the highly recursive nature of ES6 modules, which does not allow any kind of bottom-up strategy for resolving module names and paths. Error messages are rudimental right now. Probably need to track more information to make them nicer. R=svenpanne@chromium.org BUG=v8:1569 TEST= Review URL: https://chromiumcodereview.appspot.com/9615009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10966 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=rossberg@chromium.org TEST=mjsunit/object-is,mjsunit/number-is Review URL: https://chromiumcodereview.appspot.com/9630009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10965 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG=102153 TEST=regress-102153.js Review URL: https://chromiumcodereview.appspot.com/9625011 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10963 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
jkummerow@chromium.org authored
Review URL: https://chromiumcodereview.appspot.com/9623007 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10962 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 07 Mar, 2012 1 commit
-
-
mstarzinger@chromium.org authored
This adds an additional flag to control whether incremental marking should be aborted when requesting a GC, providing a finer granularity between kNoGCFlags and kMakeHeapIterableMask. R=ulan@chromium.org BUG=v8:1608 Review URL: https://chromiumcodereview.appspot.com/9608006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10961 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-