- 16 Oct, 2017 3 commits
-
-
Benedikt Meurer authored
When looking at /proc/self/maps, we need to take into account the offset in addition to the start and end addresses, otherwise --prof get's confused with binaries produced by lld. Change-Id: If6b484a8080a0393e91174c114dafe9a11964e8d Reviewed-on: https://chromium-review.googlesource.com/720371Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#48574}
-
Michael Achenbach authored
NOTRY=true TBR=sergiyb@chromium.org Bug: v8:6918 Change-Id: I16d44acd8c5cf57d472e4e8ffebf08b3d316441c Reviewed-on: https://chromium-review.googlesource.com/720370Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#48573}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/fc1d428..0db5732 TBR=machenbach@chromium.org,hablich@chromium.org Change-Id: I0fe5fdbdf90af216756c848c08d1b3b2b166c0f9 Reviewed-on: https://chromium-review.googlesource.com/720400Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#48572}
-
- 15 Oct, 2017 2 commits
-
-
Michael Achenbach authored
V8 side configs for: https://chromium-review.googlesource.com/c/chromium/tools/build/+/718938 NOTRY=true Bug: v8:6918 Change-Id: Ie375a65611c4426baafd352c0cca37d38d1a53b7 Reviewed-on: https://chromium-review.googlesource.com/718750 Commit-Queue: Michael Achenbach <machenbach@chromium.org> Reviewed-by:
Sergiy Byelozyorov <sergiyb@chromium.org> Cr-Commit-Position: refs/heads/master@{#48571}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/f630878..fc1d428 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/03a5bff..c0f385b Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/0235fed..d1283a8 TBR=machenbach@chromium.org,hablich@chromium.org Change-Id: I8c2f52e0b625f79f22dee31a704edefee1676d75 Reviewed-on: https://chromium-review.googlesource.com/720398Reviewed-by:
-
- 14 Oct, 2017 5 commits
-
-
Georg Neis authored
R=gsathya@chromium.org Bug: Change-Id: I66bc6cffddea540e382b7f59f519a4d902a0c1b6 Reviewed-on: https://chromium-review.googlesource.com/712050Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#48569}
-
Sathya Gunasekaran authored
Bug: v8:6921 Change-Id: I0ce0a285181561f1940a0a1823134fbc87e698bc Reviewed-on: https://chromium-review.googlesource.com/720237 Commit-Queue: Georg Neis <neis@chromium.org> Reviewed-by:
-
Michael Achenbach authored
This reverts commit 61292f0b. Reason for revert: Breaks layout tests: https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064/builds/18913 Original change's description: > [inspector] breakpoint after last break position should not jump to first line > > R=jgruber@chromium.org > > Bug: chromium:730177 > Change-Id: I0f3666a333604cb80bb51410c5edf2aceb0c6ef5 > Reviewed-on: https://chromium-review.googlesource.com/717717 > Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> > Reviewed-by: Jakob Gruber <jgruber@chromium.org> > Cr-Commit-Position: refs/heads/master@{#48556} TBR=kozyatinskiy@chromium.org,jgruber@chromium.org Change-Id: Ic4e961bf9c82e43281779c79e22660a55bfcb29d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:730177 Reviewed-on: https://chromium-review.googlesource.com/720376Reviewed-by:
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/c6001bd..f630878 Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/67c0157..03a5bff Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/0c09c7a..0235fed TBR=machenbach@chromium.org,hablich@chromium.org Change-Id: I22871ddb4330486a03333983b9e832d071ed2720 Reviewed-on: https://chromium-review.googlesource.com/720278Reviewed-by:
-
Mike Stanton authored
We should explain why we default to StackFrame::OPTIMIZED rather than StackFrame::INTERPRETED when we don't have a great idea about what kind of frame we are looking at. Bug: Change-Id: I9d3cc84def6164ef79a4792822d52c11dfe8a448 Reviewed-on: https://chromium-review.googlesource.com/668450Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Michael Stanton <mvstanton@chromium.org> Cr-Commit-Position: refs/heads/master@{#48565}
-
- 13 Oct, 2017 30 commits
-
-
Adam Klein authored
Bug: v8:6092, v8:6921 Change-Id: I321ecc661832f2212d16260aa6b863cef56b7676 Reviewed-on: https://chromium-review.googlesource.com/719414Reviewed-by:
-
Eric Holk authored
Enabling trap handlers has been causing problems with sanitizers, stress bots, clusterfuzz, etc. Some of these fixes will require more in depth changes. In the meantime, this restores the original behavior so the bots can turn green again. This change reverts https://crrev.com/c/673548. Bug: v8:6924 Change-Id: I4277ae53bc98f9896b800d015fda2ce68ae9e6f5 Cq-Include-Trybots: master.tryserver.v8:v8_linux64_tsan_concurrent_marking_rel_ng Reviewed-on: https://chromium-review.googlesource.com/718480Reviewed-by:
Mircea Trofin <mtrofin@chromium.org> Commit-Queue: Eric Holk <eholk@chromium.org> Cr-Commit-Position: refs/heads/master@{#48563}
-
Bill Budge authored
- Adds CodeGenerator::NeonInputOperand method for arm. - Specifies addressing mode when selecting Neon load/store. Bug: Change-Id: Iac0bb566c32882e6b9605d2978588af05493a5c7 Reviewed-on: https://chromium-review.googlesource.com/716714 Commit-Queue: Bill Budge <bbudge@chromium.org> Reviewed-by:
Ben Titzer <titzer@chromium.org> Reviewed-by:
Martyn Capewell <martyn.capewell@arm.com> Reviewed-by:
Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#48562}
-
Jakob Kummerow authored
As a simple and backmergeable fix for crbug.com/774459. Bug: chromium:774459 Tbr: bmeurer@chromium.org Change-Id: Ibe55ad13fe6be63a76dc3079a0288356ce35de9f Reviewed-on: https://chromium-review.googlesource.com/719461 Commit-Queue: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#48561}
-
Adam Klein authored
Reuses the existing logic for BigInt.parseInt, adapted slightly to allow octal and binary radix prefixes (and to support parsing of a raw character buffer, rather than a v8::internal::String). Bug: v8:6791 Change-Id: I41904b2204721eac452e0765fa9ff0ab26ee343b Reviewed-on: https://chromium-review.googlesource.com/711334 Commit-Queue: Adam Klein <adamk@chromium.org> Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Reviewed-by:
Marja Hölttä <marja@chromium.org> Reviewed-by:
Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#48560}
-
John Barboza authored
New OWNERS jbarboza and mmallick and remove bjaideep. Bug: Change-Id: I3d7b8d13cad441bd60b1d598e5553716799ef739 Reviewed-on: https://chromium-review.googlesource.com/714136Reviewed-by:
Junliang Yan <jyan@ca.ibm.com> Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Junliang Yan <jyan@ca.ibm.com> Cr-Commit-Position: refs/heads/master@{#48559}
-
Jakob Gruber authored
The type of StringIndexOf nodes is never recomputed since the operation is simply changed on the original node. Bug: chromium:769923 Change-Id: I3a2956ea69d43a56d22aff0607ac9869cf65533c Reviewed-on: https://chromium-review.googlesource.com/718758Reviewed-by:
-
Mathias Bynens authored
New code should use nullptr instead of NULL. This patch updates existing use of NULL to nullptr where applicable, making the code base more consistent. BUG=v8:6928,v8:6921 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_chromium_rel_ng;master.tryserver.v8:v8_linux_noi18n_rel_ng Change-Id: I4687f5b96fcfd88b41fa970a2b937b4f6538777c Reviewed-on: https://chromium-review.googlesource.com/718338 Commit-Queue: Mathias Bynens <mathias@chromium.org> Reviewed-by:
Andreas Haas <ahaas@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Reviewed-by:
-
Alexey Kozyatinskiy authored
R=jgruber@chromium.org Bug: chromium:730177 Change-Id: I0f3666a333604cb80bb51410c5edf2aceb0c6ef5 Reviewed-on: https://chromium-review.googlesource.com/717717 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by:
-
Mircea Trofin authored
Bug: Change-Id: Ic31aa23078cd0af04b25af9e3d06e89f45e85d88 Reviewed-on: https://chromium-review.googlesource.com/706144Reviewed-by:
Brad Nelson <bradnelson@chromium.org> Commit-Queue: Mircea Trofin <mtrofin@chromium.org> Cr-Commit-Position: refs/heads/master@{#48555}
-
Peter Marshall authored
We are trying to get rid of ZoneList now that List is gone, so here is a decent place to start. Bug: v8:6333, v8:6921 Change-Id: Ie02d3f95767a5d9946586b0efbd64ec265326fbc Reviewed-on: https://chromium-review.googlesource.com/718377Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#48554}
-
Caitlin Potter authored
Previously, Function("++f`...`) would not throw an exception until the created function was called. Now, it throws an early ReferenceError. This change matches the behaviour in JavaScriptCore and SpiderMonkey. Ordinary calls such as Function("++f()") are still thrown at runtime, also compatible with JavaScriptCore and SpiderMonkey. BUG=v8:4480, v8:6910 R=marja@chromium.org, littledan@chromium.org Change-Id: If31c6d360a0464744eff5d8dd377ebff184ae00e Reviewed-on: https://chromium-review.googlesource.com/712794 Commit-Queue: Caitlin Potter <caitp@igalia.com> Reviewed-by: -
Marja Hölttä authored
BUG=v8:5402,v8:6921 Change-Id: I96a8a7cdded6f7c37b6f1da659d63df9e3a5de2b Reviewed-on: https://chromium-review.googlesource.com/718342 Commit-Queue: Marja Hölttä <marja@chromium.org> Reviewed-by:
-
Predrag Rudic authored
Bug: Change-Id: Icc4fd48ba1313cb94102ac794b06927d24151671 Reviewed-on: https://chromium-review.googlesource.com/708270 Commit-Queue: Ivica Bogosavljevic <ivica.bogosavljevic@imgtec.com> Reviewed-by:
Ivica Bogosavljevic <ivica.bogosavljevic@imgtec.com> Cr-Commit-Position: refs/heads/master@{#48551}
-
Camillo Bruni authored
Bug: v8:6921 Change-Id: I01d6740c555acb3e9565738603bf03cedc82a077 Reviewed-on: https://chromium-review.googlesource.com/718576Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#48550}
-
Camillo Bruni authored
This should make d8 behave closer to node. Change-Id: Ic871aed194b277262d70f53cfd02a50a3447f2a4 Reviewed-on: https://chromium-review.googlesource.com/718757Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Reviewed-by:
-
Mike Stanton authored
A machine load is an effectful operation, but we didn't include it in the effect chain. Bug: v8:6929 Change-Id: I08a09c71dafd9dd7e5e40440a24751f2c5bcfae9 Reviewed-on: https://chromium-review.googlesource.com/718456 Commit-Queue: Michael Stanton <mvstanton@chromium.org> Reviewed-by:
-
Georgia Kouveli authored
This is part of JSSP removal for arm64. The padding is needed so that the extra arguments, which are pushed separately from the rest of the arguments, will take up an even number of slots, to avoid copying the rest of the arguments one slot down. Bug: v8:6644 Change-Id: I00a8730c375e4b4cc8fa0c8b6372751f92754466 Reviewed-on: https://chromium-review.googlesource.com/713255 Commit-Queue: Georgia Kouveli <georgia.kouveli@arm.com> Reviewed-by:
-
Michael Achenbach authored
NOTRY=true Bug: chromium:706728 Change-Id: I211212a922ed9f522cf735fbdce84ca5c70f93f9 Reviewed-on: https://chromium-review.googlesource.com/718705Reviewed-by:
-
Toon Verwaest authored
Bug: v8:6921 Change-Id: I9e42d0a5e7ce7fdda1d00468a82d35b973200e2c Reviewed-on: https://chromium-review.googlesource.com/718697Reviewed-by:
-
Clemens Hammacher authored
Not all interface implementations can handle unreachable code correctly. The baseline compiler will fail if it tries to pop a value from an empty stack. Instead of fixing this in the interface (the baseline compiler in this case), this CL fixes this by not calling the interface for unreachable instructions. R=titzer@chromium.org Bug: v8:6600 Change-Id: I567783ce4191ff907b2f90e73b66274728064092 Reviewed-on: https://chromium-review.googlesource.com/715638 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Ben Titzer <titzer@chromium.org> Reviewed-by:
Andreas Rossberg <rossberg@chromium.org> Reviewed-by:
-
Michael Starzinger authored
This adds and explicit check for the constructability of the new.target value in the lowering of {JSCall} nodes known to call Reflect.construct. The {JSConstruct} operator does not perform this check and relies on the implicit validity of new.target in all other use cases. R=jarin@chromium.org TEST=mjsunit/regress/regress-crbug-768080 BUG=chromium:768080 Change-Id: I7c1921e787bae64ba83de3eb08aa00fc5523e251 Reviewed-on: https://chromium-review.googlesource.com/718100Reviewed-by: -
Camillo Bruni authored
Bug: v8:6921 Change-Id: I7602cd68aec6e91e6e59ed78a5e27196e2d28835 Reviewed-on: https://chromium-review.googlesource.com/718101Reviewed-by:
-
Clemens Hammacher authored
Repeatedly allocating >1GB fails on stress bots, hence run a GC in-between to free the array buffer. R=titzer@chromium.org CC=mlippautz@chromium.org, ulan@chromium.org Bug: v8:6924 Change-Id: I44761e83f62b8225148eecbc569748cd3be21d6a Reviewed-on: https://chromium-review.googlesource.com/718109Reviewed-by:
-
sreten.kovacevic authored
First allocatable register must be same as the argument count register. This change fixes problems with optimized tests. Bug: Change-Id: I06731c7f27c5f6a761ebdeb3c3c7b2a6c14d7c1d Reviewed-on: https://chromium-review.googlesource.com/716224Reviewed-by:
-
Toon Verwaest authored
Bug: v8:6921 Change-Id: I82e0d29aba237dff22dd8dfa80ddecd7fd724df3 Reviewed-on: https://chromium-review.googlesource.com/718421Reviewed-by:
-
Michael Achenbach authored
TBR=ulan@chromium.org Bug: v8:6927 Change-Id: I6e76cc3e967b9136ed50612afb9159a404ccbfad Reviewed-on: https://chromium-review.googlesource.com/718599Reviewed-by:
-
Mythri authored
Unwinding info keeps track of the frame pointer by tracking the changes to the stack if a frame wasn't constructed. Once the frame is constructed we no longer need to keep track of this. The code generator informs the unwinding info writer about frame constructions. This information was not passed for JSFunctions calls. This cl fixes it to pass also for JSFunctions. Bug: Change-Id: Ia39980039a5f063435fa3b3ab145256909011606 Reviewed-on: https://chromium-review.googlesource.com/718596Reviewed-by:
-
Toon Verwaest authored
Bug: v8:6921 Change-Id: I9f6457812007f72b5fcc714b8baab59fc8337795 Reviewed-on: https://chromium-review.googlesource.com/718104 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Reviewed-by:
-
Toon Verwaest authored
[code-stubs] All keys in name dictionaries are internalized so stop checking in NameDictionaryLookupStub Bug: v8:6921 Change-Id: Idaa4a7e31525ccd3f599115c54845aac2fcfa430 Reviewed-on: https://chromium-review.googlesource.com/707251 Commit-Queue: Toon Verwaest <verwaest@chromium.org> Reviewed-by:
-
