- 23 Jul, 2015 7 commits
-
-
mstarzinger authored
Using the GraphBuilder base class forces each node creation to go through a virtual function dispatch just for the sake of saving the duplication of the NewNode helper methods. In total that added up to saving minus (sic!) six lines of code. R=titzer@chromium.org Review URL: https://codereview.chromium.org/1252093002 Cr-Commit-Position: refs/heads/master@{#29799}
-
yangguo authored
R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1255613002 Cr-Commit-Position: refs/heads/master@{#29798}
-
yurys authored
There is already non-throwing version FrameMirror.restart and RestartFrame in the livedit-debugger.js just adds a throwing wrapper around it. Also NEEDS_STEP_IN_PROPERTY_NAME was removed, the client code can decide based on the stack_modified field if "step in" is required. Chromium side was fixed in https://codereview.chromium.org/1249013002/ BUG=None LOG=N Review URL: https://codereview.chromium.org/1247363002 Cr-Commit-Position: refs/heads/master@{#29797}
-
Ilija.Pavlovic authored
In simulator data trace, DSLL did not print result and BAL/BGEZAL omitted result from an instruction executed in delay slot. TEST=cctest/test-assembler-mips[64] BUG= Review URL: https://codereview.chromium.org/1245173002 Cr-Commit-Position: refs/heads/master@{#29796}
-
paul.lind authored
BUG= Review URL: https://codereview.chromium.org/1249703005 Cr-Commit-Position: refs/heads/master@{#29795}
-
adamk authored
R=littledan@chromium.org BUG=v8:4311 LOG=n Review URL: https://codereview.chromium.org/1242623002 Cr-Commit-Position: refs/heads/master@{#29794}
-
v8-autoroll authored
Rolling v8/tools/clang to 4943801a353f2f58e7268e17803d87cf78f2f732 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1253623002 Cr-Commit-Position: refs/heads/master@{#29793}
-
- 22 Jul, 2015 12 commits
-
-
mstarzinger authored
R=titzer@chromium.org Review URL: https://codereview.chromium.org/1248743003 Cr-Commit-Position: refs/heads/master@{#29792}
-
danno authored
Review URL: https://codereview.chromium.org/1245523002 Cr-Commit-Position: refs/heads/master@{#29791}
-
mstarzinger authored
This preserves the context-independent entry in an optimized code map across GCs when the code is considered young (i.e. less than 3 ages). Note that any context-dependent entry for the same code will still be flushed immediately when the respective context dies, hence context lifetime is not increased. R=hpayer@chromium.org Review URL: https://codereview.chromium.org/1252463002 Cr-Commit-Position: refs/heads/master@{#29790}
-
mvstanton authored
It's just the same as StoreTransitionDescriptor. BUG= Review URL: https://codereview.chromium.org/1248973002 Cr-Commit-Position: refs/heads/master@{#29789}
-
mstarzinger authored
This allows the optimized code map to contain no context-dependent entries, but still hold one context-independent entry. This is a precursor to extending the lifetime of the context-independent entry. R=mvstanton@chromium.org Review URL: https://codereview.chromium.org/1249543005 Cr-Commit-Position: refs/heads/master@{#29788}
-
mstarzinger authored
This fixes a recent regression where the register holding the original receiver was pushed onto the stack before the internal frame within the CallStubInRecordCallTarget helper was created. That in turn confused the stack walker when allocations in these stubs failed. R=mvstanton@chromium.org BUG=chromium:512711 LOG=N Review URL: https://codereview.chromium.org/1245043003 Cr-Commit-Position: refs/heads/master@{#29787}
-
jochen authored
The layout of fixed typed array base is then capable of handling external typed arrays as well. In a follow-up CL, I'll delete external typed arrays, and use fixed typed array base instead BUG=v8:3996 R=jarin@chromium.org,mstarzinger@chromium.org LOG=n Review URL: https://codereview.chromium.org/1248483007 Cr-Commit-Position: refs/heads/master@{#29786}
-
mstarzinger authored
This fixes a recent regression where the register usually holding the original receiver was pushed onto the stack even when the stub was not compiled for super calls (i.e. IsSuperConstructorCall). This led to untagged values being present in the stack frame. R=jacob.bramley@arm.com BUG=chromium:512573 LOG=N Review URL: https://codereview.chromium.org/1241223003 Cr-Commit-Position: refs/heads/master@{#29785}
-
yangguo authored
The background parser checks for debugger state in its constructor. This is not good enough, since the debugger state may change afterwards, but before compiling takes place. As the background parser can only parse lazily, this could mean that due to debugging, we try to eagerly compile an inner function we have not eagerly parsed. R=jochen@chromium.org Review URL: https://codereview.chromium.org/1247743002 Cr-Commit-Position: refs/heads/master@{#29784}
-
mtrofin authored
Unit tests for the live range conflict detection mechanism (CoalescedLiveRanges) in the Greedy Allocator. Consolidated conflict detection and traversal logic in CoalescedLiveRanges to avoid duplication in both code and testing. In addition, this change achieves better separation between CoalescedLiveRanges and other register allocator components, improving testability and maintainability. BUG= Review URL: https://codereview.chromium.org/1219063017 Cr-Commit-Position: refs/heads/master@{#29783}
-
v8-autoroll authored
Rolling v8/third_party/android_tools to 6a7921fdbc510e30de5bb38c5dcf9e524713ca6b TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1247753003 Cr-Commit-Position: refs/heads/master@{#29782}
-
bbudge authored
LOG=N BUG=v8:4124 Review URL: https://codereview.chromium.org/1239423004 Cr-Commit-Position: refs/heads/master@{#29781}
-
- 21 Jul, 2015 16 commits
-
-
bradnelson authored
LOG=N BUG=None TEST=manual,local R=bbudge@chromium.org,machenbach@chromium.org Review URL: https://codereview.chromium.org/1240453003 Cr-Commit-Position: refs/heads/master@{#29780}
-
adamk authored
Many mjsunit tests (as well as the promises-aplus adapter scripts) were using Object.observe simply for microtask-enqueueing purposes. Replaced such uses with %EnqueueMicrotask. Review URL: https://codereview.chromium.org/1246933002 Cr-Commit-Position: refs/heads/master@{#29779}
-
hpayer authored
This reverts commit 80b3f169. Revert "Record code slots that may point to evacuation candidate objects after deoptimizing them." This reverts commit 4621210c. BUG=chromium:507840 LOG=n Review URL: https://codereview.chromium.org/1239383004 Cr-Commit-Position: refs/heads/master@{#29778}
-
rmcilroy authored
The InterpreterAssembler needs to specify a specific CallDescriptor type instead of using the SimplifiedCDescriptor type. This CL makes it possible to specify the CallDescriptor used by the RawMachineAssembler instead of specifying a MachineSignature. Also removes instruction-selector-tester.h which was erroneously resurrected at some point. BUG=v8:4280 LOG=N Review URL: https://codereview.chromium.org/1235313002 Cr-Commit-Position: refs/heads/master@{#29777}
-
ulan authored
This is required in order for Globals to be stored in STL containers. Patch from Aaron Link <aaronlink@google.com> BUG= Review URL: https://codereview.chromium.org/1244033002 Cr-Commit-Position: refs/heads/master@{#29776}
-
dstence authored
Revisit of https://codereview.chromium.org/910333004. Use 4MB heap page size over the default of 1MB. This change provides an improvement of 1.86% on the composite octane benchmark score on PPC. This is 0.56% more than if --min_semi_space_size=4 was used to specify a 4MB heap page size. Additionally, two more tests required modification to account for configurable heap page size. R=svenpanne@chromium.org, hpayer@chromium.org, danno@chromium.org, mbrandy@us.ibm.com, michael_dawson@ca.ibm.com BUG= Review URL: https://codereview.chromium.org/1221433022 Cr-Commit-Position: refs/heads/master@{#29775}
-
mstarzinger authored
R=jacob.bramley@arm.com Review URL: https://codereview.chromium.org/1244023002 Cr-Commit-Position: refs/heads/master@{#29774}
-
mstarzinger authored
R=jacob.bramley@arm.com Review URL: https://codereview.chromium.org/1245153002 Cr-Commit-Position: refs/heads/master@{#29773}
-
ulan authored
BUG=v8:4277 LOG=NO Review URL: https://codereview.chromium.org/1251443002 Cr-Commit-Position: refs/heads/master@{#29772}
-
epertoso authored
Always run the second pass of the phantom callbacks synchronously if --predictable or --optimize_for_size are set. R=jochen@chromium.org Review URL: https://codereview.chromium.org/1245093004 Cr-Commit-Position: refs/heads/master@{#29771}
-
aperez authored
The gdb-v8-support.py script uses the "re" module to match regular expression, but it does not import it, resulting in an error when loading the script from GDB. This patch adds the missing import. BUG= Review URL: https://codereview.chromium.org/1245713002 Cr-Commit-Position: refs/heads/master@{#29770}
-
machenbach authored
Also remove deprecated android_arm configs. TBR=bradnelson@chromium.org NOTRY=true Review URL: https://codereview.chromium.org/1244003002 Cr-Commit-Position: refs/heads/master@{#29769}
-
mlippautz authored
BUG= Review URL: https://codereview.chromium.org/1235913002 Cr-Commit-Position: refs/heads/master@{#29768}
-
binji authored
R=jochen@chromium.org LOG=n Review URL: https://codereview.chromium.org/1242973002 Cr-Commit-Position: refs/heads/master@{#29767}
-
v8-autoroll authored
Rolling v8/tools/clang to 33c2e4149926da7262361323a111605877add859 TBR=machenbach@chromium.org Review URL: https://codereview.chromium.org/1247693002 Cr-Commit-Position: refs/heads/master@{#29766}
-
chunyang.dai authored
port 35c28ce0 (r29758). original commit message: Prior to this patch, we enter a global debug mode whenever a break point is set. By entering this mode, all code is deoptimized and activated frames are recompiled and redirected to newly compiled debug code. After this patch, we only deoptimize/redirect for functions we want to debug. Trigger for this is Debug::EnsureDebugInfo, and having DebugInfo object attached to the SFI prevents optimization/inlining. The result is that we can have optimized code for functions without break points alongside functions that do have break points, which are not optimized. BUG= Review URL: https://codereview.chromium.org/1249503002 Cr-Commit-Position: refs/heads/master@{#29765}
-
- 20 Jul, 2015 5 commits
-
-
mbrandy authored
Port 35c28ce0 Original commit message: Prior to this patch, we enter a global debug mode whenever a break point is set. By entering this mode, all code is deoptimized and activated frames are recompiled and redirected to newly compiled debug code. After this patch, we only deoptimize/redirect for functions we want to debug. Trigger for this is Debug::EnsureDebugInfo, and having DebugInfo object attached to the SFI prevents optimization/inlining. The result is that we can have optimized code for functions without break points alongside functions that do have break points, which are not optimized. R=yangguo@chromium.org, dstence@us.ibm.com, michael_dawson@ca.ibm.com BUG=v8:4132 LOG=N Review URL: https://codereview.chromium.org/1244823002 Cr-Commit-Position: refs/heads/master@{#29764}
-
danno authored
In many cases, the context that TurboFan's ASTGraphBuilder or subsequent reduction operations attaches to nodes does not need to be that exact context, but rather only needs to be one with the same native context, because it is used internally only to fetch the native context, e.g. for creating and throwing exceptions. This reducer recognizes common cases where the context that is specified for a node can be relaxed to a canonical, less specific one. This relaxed context can either be the enclosing function's context or a specific Module or Script context that is explicitly created within the function. This optimization is especially important for TurboFan-generated code stubs which use context specialization and inlining to generate optimal code. Without context relaxation, many extraneous moves are generated to pass exactly the right context to internal functions like ToNumber and AllocateHeapNumber, which only need the native context. By turning context relaxation on, these moves disappear because all these common internal context uses are unified to the context passed into the stub function, which is typically already in the correct context register and remains there for short stubs. It also eliminates the explicit use of a specialized context constant in the code stub in these cases, which could cause memory leaks. Review URL: https://codereview.chromium.org/1244583003 Cr-Commit-Position: refs/heads/master@{#29763}
-
mstarzinger authored
Note that this just narrows the existing workaround for any 'this' in derived constructors (having a temporal dead zone) so that we can still recognize static cases correctly (i.e. when 'this' is provably outside or inside the temporal dead zone). R=rossberg@chromium.org Review URL: https://codereview.chromium.org/1245653002 Cr-Commit-Position: refs/heads/master@{#29762}
-
epertoso authored
R=jochen@chromium.org,yangguo@chromium.org Review URL: https://codereview.chromium.org/1231663007 Cr-Commit-Position: refs/heads/master@{#29761}
-
jochen authored
This will be used to compute the base pointer of the new unified representation for both on-heap and external typed arrays. The idea is that either the external or the tagged pointer is 0 (although in practice, if the tagged pointer is non-0, the external pointer will contain the offset from the start of the on-heap typed array to the data in the on-heap typed array). The HAdd is marked as depending on new-space promotion, as the tagged pointer might move during GC, and so the result of the addition needs to be recomputed. BUG=v8:3996 R=jarin@chromium.org LOG=n Review URL: https://codereview.chromium.org/1244693002 Cr-Commit-Position: refs/heads/master@{#29760}
-