- 07 Apr, 2009 6 commits
-
-
sgjesse@chromium.org authored
TBR=erik.corry@gmail.com Review URL: http://codereview.chromium.org/62103 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1686 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/62102 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1685 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sgjesse@chromium.org authored
For function.call debug step in did not work as execution did not break in the function called. This has now been fixed using the same means as for function.apply in CL http://codereview.chromium.org/63055. Review URL: http://codereview.chromium.org/63058 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1684 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sgjesse@chromium.org authored
The generic step-in mechanism floods the function called with break points to ensure a break is hit when entering the function. This generic mechanism was also used for function.apply. The code for function.apply contains a keyed load IC which was patched when stepping into function.apply. However function.apply enteres an internal frame not a JavaScript frame. This caused the logic for returning from the break in function.apply to fail as it forced a jump to the IC on the top JavaScript frame. The top JavaScript frame was the frame for the function calling function.apply not the frame for the apply function. Now returning from the break point in the keyed load IC in the apply code caused a jump to the code for the call IC for the function calling function.apply in the first place. Not a pretty sight. Step-in now handles function.apply as a separate case where the actual JavaScript function called through apply is flodded with breakpoints instead of the function.apply function. BUG=269 BUG=8210@chromium.org Review URL: http://codereview.chromium.org/63055 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1683 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sgjesse@chromium.org authored
Reviewed CL at http://codereview.chromium.org/42686. BUG=96 Review URL: http://codereview.chromium.org/62052 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1681 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kasperl@chromium.org authored
Review URL: http://codereview.chromium.org/62091 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1680 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 06 Apr, 2009 2 commits
-
-
davemoore@chromium.org authored
Review URL: http://codereview.chromium.org/56185 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1679 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
whesse@chromium.org authored
Review URL: http://codereview.chromium.org/63010 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1678 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 03 Apr, 2009 6 commits
-
-
whesse@chromium.org authored
Review URL: http://codereview.chromium.org/56151 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1677 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
lrn@chromium.org authored
Special case for NaN in equality test. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1676 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
lrn@chromium.org authored
Uses static string type to optimize string additions. git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1675 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
to V8's heap. Review URL: http://codereview.chromium.org/60089 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1674 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
one in v8::V8::Initialize to after the early bailout. Review URL: http://codereview.chromium.org/60083 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1673 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
V8's heap or only need read access. This means that IsDeadCeck and EnsureInitialized could sometimes be called without having already entered the VM. To simplify things, this is made always the case. A couple of error callbacks do not need to leave V8 because they haven't entered. Consistently enter V8 after LOG_API (since LOG_API is sometimes before EnsureInitialized or IsDeadCheck). This all should have no effect unless V8 is built with ENABLE_HEAP_PROTECTION and run with --protect-heap. Review URL: http://codereview.chromium.org/56211 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1672 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 02 Apr, 2009 3 commits
-
-
ager@chromium.org authored
variables in our scons setup. Here is an example of importing an additional environment variable: export MYVAR='value' scons importenv="MYVAR" Review URL: http://codereview.chromium.org/60046 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1671 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
constants and copies below the watermark on backward jump targets (that's the whole point!). Review URL: http://codereview.chromium.org/60044 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1670 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
counting the reference to the return value and passing it to the return label. This requires threading it through try/catch and try/finally. The return value is loaded into eax more lazily than before. Also, perform some related refactoring of jump targets. Review URL: http://codereview.chromium.org/56172 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1669 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 01 Apr, 2009 5 commits
-
-
ager@chromium.org authored
compiler optimization which has now been reverted. Review URL: http://codereview.chromium.org/60011 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1667 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ager@chromium.org authored
TBR=whesse@chromium.org Review URL: http://codereview.chromium.org/60010 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1666 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
lrn@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1665 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sgjesse@chromium.org authored
Changelist http://codereview.chromium.org/56056 was committed directly to trunk by addident. Review URL: http://codereview.chromium.org/60005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1662 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ager@chromium.org authored
number of bug fixes. Review URL: http://codereview.chromium.org/60004 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1661 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 31 Mar, 2009 16 commits
-
-
ager@chromium.org authored
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1660 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ager@chromium.org authored
test.py for running the simulator tests. Mark the exception propagation tests as failing on ARM in general for now. I'll dig into it again tomorrow morning. TRB=christian.plesner.hansen@gmail.com Review URL: http://codereview.chromium.org/56112 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1659 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
ager@chromium.org authored
Fix exception propagation problem where undefined was returned instead of an empty handle in case of an exception. This problem can break C++ programs that are not interested in catching exceptions and just want to propagate them out by testing for empty handles. The issue is that exceptions are not rescheduled if they are externally caught. Externally caught exceptions have to be rescheduled if there is a JavaScript frame on the way to the C++ frame that holds the external handler. A couple of tests will fail on the ARM simulator because the simulator has separate stacks for C++ and JavaScript. I have marked the tests as failing only on the simulator. Review URL: http://codereview.chromium.org/56105 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1657 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
whesse@chromium.org authored
Review URL: http://codereview.chromium.org/56106 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1656 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
frame elements when allocating them to a register as a result of popping one of their copies. Review URL: http://codereview.chromium.org/57053 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1655 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/57056 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1654 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/57055 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1653 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/57054 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1652 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Review URL: http://codereview.chromium.org/56110 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1651 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
* Remove the non-working methods from the os object on d8 on Windows so you can test for their presence with if (os.system). * Add a test (not run by default since it only works on d8). * Fix incorrect use of wait that left defunct processes (zombies). Review URL: http://codereview.chromium.org/56107 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1650 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sgjesse@chromium.org authored
Fixed the OS check in the SCons build. Moved SetEnvironment to platform file as Windows does not have setenv. Added the d8-windows.cc to the Visual Studio project. Review URL: http://codereview.chromium.org/57050 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1649 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
sgjesse@chromium.org authored
Add a semaphore for accessing debugger varaibles which can be changed from a different thread. This is mainly the debug message handler which can be set to NULL to disconnect the debugger. Control the unloading of the debugger from the V8 thread. Before the debugger unload was called from the thread setting the debug message handler to NULL. This was not safe as this involves calling into V8. This change handles the unloading of the debugger either when entering a debugger event and the debugger was disconnected while the debugger was not active or when leaving the debugger and the debugger was disconnected while the debugger was active. Add a flag to avoid unloading the debugger if debugger code is used by the application for other purposes than debugging. Added tests for clearing the debug message handler. Review URL: http://codereview.chromium.org/56102 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1648 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
Indiscriminately mark every place with EnsureInitialized, ON_BAILOUT, or IsDeadCheck (even if they cannot write to V8's heap). Also mark callbacks, and one other place (Function::SetName) hit in Chromium. Review URL: http://codereview.chromium.org/57049 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1647 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
mikhail.naganov@gmail.com authored
on a real web application loaded in the test shell. Also implemented output of JSON-encoded call stacks for profiler prototype. Review URL: http://codereview.chromium.org/56064 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1646 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
kmillikin@chromium.org authored
oprofile agent when we compile the body of a function literal. Review URL: http://codereview.chromium.org/57048 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1645 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
erik.corry@gmail.com authored
Protect os.chdir, os.setenv, os.system against string conversion failures. Add comment about the issue to include/v8.h. Review URL: http://codereview.chromium.org/57005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1644 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
- 30 Mar, 2009 2 commits
-
-
kmillikin@chromium.org authored
(generic state inside V8) in the API to allow the V8 shell to run all the mjsunit tests with heap protection on. These state changes are only taken when built with ENABLE_HEAP_PROTECTION. The two states OTHER and EXTERNAL are treated the same because we will not properly reenter OTHER through the API. Review URL: http://codereview.chromium.org/56060 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1643 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-
whesse@chromium.org authored
Review URL: http://codereview.chromium.org/57006 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1641 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
-