- 22 Sep, 2011 10 commits
-
-
mstarzinger@chromium.org authored
R=svenpanne@chromium.org BUG=v8:1707 TEST=cctest/test-heap/GrowAndShrinkNewSpace Review URL: http://codereview.chromium.org/7995004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9398 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ricow@chromium.org authored
Filled issue 1718 to track this. Review URL: http://codereview.chromium.org/7995003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9397 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
R=mstarzinger@chromium.org BUG=v8:1543,v8:1565 TEST= Review URL: http://codereview.chromium.org/7754015 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9396 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
Review URL: http://codereview.chromium.org/7989003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9395 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=vegorov@chromium.org BUG=v8:1708 TEST=mjsunit/regress/regress-1708 Review URL: http://codereview.chromium.org/7979038 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9394 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
This avoid unwanted sharing between different function prototypes and in general should help inlining because constant function properties on one prototype don't affect other prototypes anymore. BUG=v8:1716 Review URL: http://codereview.chromium.org/7994001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9393 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
danno@chromium.org authored
Activated by the flag --smi-only-arrays Currently not crankshaft support, using flag on non-ia32 platforms will lead to write barrier misses and crashes. BUG=none TEST=elements_kind.js Review URL: http://codereview.chromium.org/7901016 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9392 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
Rehome some Object/JSReceiver/JSObject methods. R=ricow@chromium.org,kmillikin@chromium.org BUG=v8:1543 TEST= Review URL: http://codereview.chromium.org/7795055 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9381 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
Review URL: http://codereview.chromium.org/7980064 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9372 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG=v8:1711 TEST=mjsunit/regress/regress-1711.js Review URL: http://codereview.chromium.org/7976046 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9371 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 21 Sep, 2011 14 commits
-
-
rossberg@chromium.org authored
of the range of proper JS objects. Unfortunately, callable types no longer form a range now. However, there are only two anyway. We put them at either end of the range of JS object types so that certain compares can be combined. R=erik.corry@gmail.com,kmillikin@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7737036 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9370 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
Review URL: http://codereview.chromium.org/7983033 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9369 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sgjesse@chromium.org authored
If the file test.js contains: function f() { debugger; } f() Then running $ d8 --debugger test.js will now hit the breakpoint in f which it would not before. R=yangguo@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org//7981023 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9366 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
Original code review: http://codereview.chromium.org/7889046/ Review URL: http://codereview.chromium.org/7978028 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9365 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
R=kmillikin@chromium.org BUG=v8:1543 TEST= Review URL: http://codereview.chromium.org/7828080 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9364 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
keuchel@chromium.org authored
The preparser has been out of sync with the parser. As a reminder, we have the following grammer for harmony mode Block :: { SourceElement* } SourceElement :: Statement FunctionDeclaration LetDeclaration instead of Block :: { Statement* } SourceElement :: Statement FunctionDeclaration The extension to allow FunctionDeclarations in statement positions in non-strict code is still active. Review URL: http://codereview.chromium.org/7983006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9363 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vegorov@chromium.org authored
Otherwise we get the wrong page when start == limit. R=lrn@chromium.org Review URL: http://codereview.chromium.org/7979019 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9362 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG=v8:1573 TEST=cctest test-debug/TestDebuggerAgent Review URL: http://codereview.chromium.org/7978025 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9361 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vegorov@chromium.org authored
When aborting incremental marking with compaction discard all slots collected on evacuation candidates. R=ricow@chromium.org BUG=v8:1700 TEST=inspector/debugger/debugger-step-in.html Review URL: http://codereview.chromium.org/7977004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9360 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
rossberg@chromium.org authored
R=jkummerow@chromium.org BUG=v8:1698 TEST= Review URL: http://codereview.chromium.org/7977021 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9358 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
Last minute cleanup lost a '*'. TBR=ricow@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7977020 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9357 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
The threading test failures seem to be due to a GC-unsafe place, that mixed handles and raw pointers, in the runtime code for context lookup. R=fschneider@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7890002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9356 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
This is not perfect, but it should fix the problem at hand. We should really clean up the memory handling responsibilities for the (macro)assemblers. BUG=v8:1706 Review URL: http://codereview.chromium.org/7978023 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9351 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/7978022 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9350 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 20 Sep, 2011 16 commits
-
-
mstarzinger@chromium.org authored
This prevents potential misuse of SeqString::kHeaderSize as in the case of live byte counting in incremental marking stub. All stubs picked up the undefined size constant SeqString::kHeaderSize, thus the computed size of all strings was off by two pointers slots. R=lrn@chromium.org BUG=v8:1672 TEST=mjsunit/object-seal.js,... Review URL: http://codereview.chromium.org/7971009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9349 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=vegorov@chromium.org BUG=v8:1702 TEST=cctest/test-heap/GrowAndShrinkNewSpace Review URL: http://codereview.chromium.org/7983001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9348 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
The formerly unused variable was found by GCC 4.6.1, BTW... Review URL: http://codereview.chromium.org/7979005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9347 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mstarzinger@chromium.org authored
R=lrn@chromium.org BUG=v8:1702 TEST=cctest/test-heap/GrowAndShrinkNewSpace Review URL: http://codereview.chromium.org/7976003 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9346 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vegorov@chromium.org authored
R=erik.corry@gmail.com Review URL: http://codereview.chromium.org/7980004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9345 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Fix some incorrect comments. Review URL: http://codereview.chromium.org/7977005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9344 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
vegorov@chromium.org authored
We should not use slot address to find out the page. This does not work for large pages. Also this assertion is not always true (violated during incremental marking). R=erik.corry@gmail.com TEST=mozilla/js1_5/extensions/regress-371636 Review URL: http://codereview.chromium.org/7981001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9339 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
lrn@chromium.org authored
The "live bytes" count is *really* a "marked black" count - i.e., the count of bytes *known* to be live. Fix aggravating bug on X64 where assembler code used a value that was off by a factor of 2^31. Ensure that sweeping clears live-bytes. Added other missing increments. Added print statements to trace live-byte modifications, under a flag. Still a few cases of undercounting left. (New issue to merge from GC branch to bleeding_edge) Review URL: http://codereview.chromium.org/7970009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9338 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
We have to check for uninitialized uses before phi-elimination. Otherwise we may miss such a use and result in using the hole value instead. This causes a NULL-dereference or assertion failure. BUG=96989 TEST=mjsunit/compiler/regress-96989.js Review URL: http://codereview.chromium.org/7974009 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9337 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
object. Rename it to be the inner pointer to code cache. Review URL: http://codereview.chromium.org/7969013 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9336 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
yangguo@chromium.org authored
BUG=94873 Review URL: http://codereview.chromium.org/7929001 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9335 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
Review URL: http://codereview.chromium.org/7969014 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9334 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
svenpanne@chromium.org authored
Review URL: http://codereview.chromium.org/7970008 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9333 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
the new large pages it takes too long to iterate from the start of the page to find a code object. Review URL: http://codereview.chromium.org/7974007 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9332 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
We reset the count of outgoing arguments, used for the index in the frame's outgoing arguments, for each level of inlining. This could result in the arguments overlapping, rather than stacking on top of each other. R=whesse@chromium.org,fschneider@chromium.org BUG= TEST= Review URL: http://codereview.chromium.org/7932022 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9331 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
fschneider@chromium.org authored
BUG=v8:1698 Review URL: http://codereview.chromium.org/7974006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@9330 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-