- 31 Mar, 2017 1 commit
-
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/a634e44..673a8f4 Rolling v8/third_party/android_tools: https://chromium.googlesource.com/android_tools/+log/b43a6a2..b65c477 Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/d3a9107..b13bd47 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/c55112f..5bc7c5e TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Change-Id: I0c0febc9be9fe1d38ffedfb1d92588e6871541fc Reviewed-on: https://chromium-review.googlesource.com/464446Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#44286}
-
- 30 Mar, 2017 29 commits
-
-
kozyatinskiy authored
This step is required to implement console as builtin which calls console delegate methods. BUG=v8:6175 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2783073002 Cr-Original-Commit-Position: refs/heads/master@{#44283} Committed: https://chromium.googlesource.com/v8/v8/+/fe27dccd873024213b16d1e9810dda6a6c705571 Review-Url: https://codereview.chromium.org/2783073002 Cr-Commit-Position: refs/heads/master@{#44285}
-
kozyatinskiy authored
Revert of [inspector] convert V8Console static methods into members (patchset #2 id:20001 of https://codereview.chromium.org/2783073002/ ) Reason for revert: Too many simulatenously landed CLs, this one should be rebased first. Original issue's description: > [inspector] convert V8Console static methods into members > > This step is required to implement console as builtin which calls console delegate methods. > > BUG=v8:6168 > R=dgozman@chromium.org > > Review-Url: https://codereview.chromium.org/2783073002 > Cr-Commit-Position: refs/heads/master@{#44283} > Committed: https://chromium.googlesource.com/v8/v8/+/fe27dccd873024213b16d1e9810dda6a6c705571 TBR=dgozman@chromium.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=v8:6168 Review-Url: https://codereview.chromium.org/2793443002 Cr-Commit-Position: refs/heads/master@{#44284}
-
kozyatinskiy authored
This step is required to implement console as builtin which calls console delegate methods. BUG=v8:6168 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2783073002 Cr-Commit-Position: refs/heads/master@{#44283}
-
kozyatinskiy authored
In inspector code everywhere except V8StackTraceImpl we get pointer to isolate from inspector object or v8::FunctionCallbackInfo. We can avoid usage of v8::Isolate::GetCurrent in V8StackTraceImpl too. It will simplify a little embedder code by removing requirement to have v8::Isolate::Scope before calling to V8InspectorSession::dispatchProtocolMessage. BUG=v8:5907 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2789593002 Cr-Commit-Position: refs/heads/master@{#44282}
-
kschimpf authored
BUG=chromium:704922 R=bbudge@chromium.org,bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2786193002 Cr-Commit-Position: refs/heads/master@{#44281}
-
Franziska Hinkelmann authored
R=adamk@chromium.org, mstarzinger@chromium.org BUG= Change-Id: Ibac495e93b523bd034cc9f2d9e3a43cf38c9ab14 Reviewed-on: https://chromium-review.googlesource.com/463368Reviewed-by:
Adam Klein <adamk@chromium.org> Commit-Queue: Franziska Hinkelmann <franzih@chromium.org> Cr-Commit-Position: refs/heads/master@{#44280}
-
sampsong authored
R=dgozman@chromium.org, kozyatinskiy@chromium.org, bjaideep@ca.ibm.com, jyan@ca.ibm.com, joransiu@ca.ibm.com BUG= Review-Url: https://codereview.chromium.org/2787713003 Cr-Commit-Position: refs/heads/master@{#44279}
-
Caitlin Potter authored
Currently, async generators are stringified the same way normal Generators are. This change prefixes async generator methods with "async *", and other async generator functions with "async function* ". BUG=v8:5855 R=adamk@chromium.org, littledan@chromium.org, jwolfe@igalia.com Change-Id: Ia809fad64caac4464dbc9f7fa7728584d0f67832 Reviewed-on: https://chromium-review.googlesource.com/463526 Commit-Queue: Caitlin Potter <caitp@igalia.com> Reviewed-by:
-
Andreas Haas authored
It makes no sense to check if unaligned accesses of bytes in memory are allowed, since these accesses are always aligned. There was a problem on mips that we created an UnalignedLoad(Int8), which was, however, not implemented in the mips instruction selector. R=clemensh@chromium.org Change-Id: I20369e078e3c24942aa90c2bd3333d9881de0072 Reviewed-on: https://chromium-review.googlesource.com/463006Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#44277}
-
Andreas Haas authored
The test was out-dated. The wasm bytes still had the version 0xd, and no END instruction at the end of the function. In addition, the test used asynchronous compilation but did not wait for the promise to resolve. R=clemensh@chromium.org Change-Id: Ib01f47ac8f668401ed14470af7100e990e5bbd94 Reviewed-on: https://chromium-review.googlesource.com/463286Reviewed-by:
-
Adam Klein authored
BUG=v8:4958 Change-Id: Id02d36fce76eed54a5a3d348dbac2ea7d43f4ef3 Reviewed-on: https://chromium-review.googlesource.com/462336Reviewed-by:
Daniel Ehrenberg <littledan@chromium.org> Commit-Queue: Adam Klein <adamk@chromium.org> Cr-Commit-Position: refs/heads/master@{#44275}
-
tebbi authored
R=mvstanton@chromium.org,danno@chromium.org Review-Url: https://codereview.chromium.org/2775203002 Cr-Commit-Position: refs/heads/master@{#44274}
-
Michael Starzinger authored
R=machenbach@chromium.org BUG=v8:6127 Change-Id: If029d449aedb6c10ec14aa847a2b68e6ce46ef94 Reviewed-on: https://chromium-review.googlesource.com/463046Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#44273}
-
Michael Achenbach authored
Bug: chromium:645890 Change-Id: If34ac1336d0ee3c23e89050aef2cf30b754b67c1 Reviewed-on: https://chromium-review.googlesource.com/461145 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Reviewed-by:
Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Cr-Commit-Position: refs/heads/master@{#44272}
-
mvstanton authored
HasOrigin() can allocate. Make sure to wrap vulnerable raw pointers in handles. BUG= Review-Url: https://codereview.chromium.org/2788663002 Cr-Commit-Position: refs/heads/master@{#44271}
-
kozyatinskiy authored
BUG=chromium:432469 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2746743002 Cr-Commit-Position: refs/heads/master@{#44270}
-
Camillo Bruni authored
- Add new address markers: T: tagged pointer in the minidump C: address into a module in the minidump S: pointer into the exception stack in the minidump *: other address in the minidump - Show ASCII decoding of address in dd - Display potential frame markers on the exception stack: 00000032212fdae8: 0000000300000000 ........ Smi(3) EXIT frame marker - Display relative addresses, useful to detect stack frames: 00000032212fdb68: 00000032212fdb98 S ........ [+6]=00000032212fdcb0 S 00000032212fdb70: 0000010ff5ca0a84 ........ 00000032212fdb78: 000001064c1fa881 ........ 00000032212fdb80: 0000016a8e52fcb1 ........ 00000032212fdb88: 0000010ff5ca0981 ........ 00000032212fdb90: 0000000d00000000 ........ Smi(13) INTERNAL frame marker 00000032212fdb98: 00000032212fdcb0 S ........ [+35]=00000032212fdd61 S Change-Id: I56bd7e6723a34bcb668719246dd5ff2898224928 Reviewed-on: https://chromium-review.googlesource.com/461862Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Commit-Queue: Camillo Bruni <cbruni@chromium.org> Cr-Commit-Position: refs/heads/master@{#44269}
-
hpayer authored
BUG=v8:5807 Review-Url: https://codereview.chromium.org/2781363002 Cr-Commit-Position: refs/heads/master@{#44268}
-
jgruber authored
GetProperty(result, groups) needs to be called iff the harmony-regexp-named-captures flag is enabled. Also add a couple of DCHECKS. BUG=v8:5437,chromium:706748 Review-Url: https://codereview.chromium.org/2786933002 Cr-Commit-Position: refs/heads/master@{#44267}
-
vchigrin authored
Compiler-generated copy constructor does not generate correct code for this class, so make it move-only type. Review-Url: https://codereview.chromium.org/2781993005 Cr-Commit-Position: refs/heads/master@{#44266}
-
Peter Marshall authored
We don't use it anywhere anymore. BUG= Change-Id: I9acd9c427c6af7422bbdf58088b61ceafd1ee655 Reviewed-on: https://chromium-review.googlesource.com/462968Reviewed-by:
Camillo Bruni <cbruni@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#44265}
-
bmeurer authored
The inlining logic doesn't account for the fact that the derived constructor could return a primitive, thus leaking the implicit receiver (which is the hole). R=jarin@chromium.org BUG=chromium:706642 Review-Url: https://codereview.chromium.org/2788603002 Cr-Commit-Position: refs/heads/master@{#44264}
-
Andreas Haas authored
The source set only contained a header file, which caused problems when compiling a static library with VS. R=machenbach@chromium.org BUG=v8:6158 Change-Id: I3eed4a888e72cf6a2917190e4a1db7b38006cd0c Reviewed-on: https://chromium-review.googlesource.com/463027Reviewed-by:
-
Franziska Hinkelmann authored
The parameter indices are shifted by 1 in BytecodeArrayBuilder because the receiver is variable at index 0 and not -1. Split BytecodeArrayBuilder::Parameter(index) method into Receiver() (same as Parameter(-1)) and Parameter(index). This way we avoid confusing (index+1) counting in BytecodeGenerator(). BUG= Change-Id: Id87ec7c708cecfc3108011994f3177f483772bcc Reviewed-on: https://chromium-review.googlesource.com/461904Reviewed-by:
Ross McIlroy <rmcilroy@chromium.org> Commit-Queue: Franziska Hinkelmann <franzih@chromium.org> Cr-Commit-Position: refs/heads/master@{#44262}
-
Michael Starzinger authored
R=clemensh@chromium.org BUG=v8:6127 Change-Id: I5e1b0d3efdf7f4aede7da83a35c072b5ac85d5c7 Reviewed-on: https://chromium-review.googlesource.com/463026Reviewed-by:
-
Michael Starzinger authored
R=clemensh@chromium.org BUG=v8:6127 Change-Id: I32d2a36cdc2a65c3e0016e49157524573755d09d Reviewed-on: https://chromium-review.googlesource.com/461185 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
Brad Nelson <bradnelson@chromium.org> Cr-Commit-Position: refs/heads/master@{#44260}
-
bmeurer authored
Recognize the Boolean constructor calls in JSCallReducer and replace them with simple JSToBoolean nodes. R=yangguo@chromium.org BUG=v8:5267,v8:6169 Review-Url: https://codereview.chromium.org/2782143003 Cr-Commit-Position: refs/heads/master@{#44259}
-
v8-autoroll authored
Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/133db8f..a634e44 Rolling v8/third_party/catapult: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+log/0c870c7..d3a9107 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/e9e483c..c55112f TBR=machenbach@chromium.org,vogelheim@chromium.org,hablich@chromium.org Change-Id: I06d2c4aa29c143c1c8198d109679db2341532507 Reviewed-on: https://chromium-review.googlesource.com/462596Reviewed-by:
-
bjaideep authored
Implemented l[w|h|b]arx and st[w|h|b]cx instructions which are needed to perform atomic exchange. Also added synchronization primitives similar to arm to simulate those instructions. R=joransiu@ca.ibm.com, jyan@ca.ibm.com, binji@chromium.org, aseemgarg@chromium.org BUG= Review-Url: https://codereview.chromium.org/2754263004 Cr-Commit-Position: refs/heads/master@{#44257}
-
- 29 Mar, 2017 10 commits
-
-
kozyatinskiy authored
We need to split creating of console and installing memory getter and remove console.assert hack before migration to builtin. We can implement super fast console.assert after migration. BUG=chromium:588893 R=dgozman@chromium.org TBR=yangguo@chromium.org Review-Url: https://codereview.chromium.org/2781883003 Cr-Commit-Position: refs/heads/master@{#44256}
-
kschimpf authored
Do final change to Chrome flags so that UMA will start collecting separate statistics, using a "histogram_suffixes" format. Corresponding changes to chromium are in: CL https://codereview.chromium.org/2781163002 BUG=chromium:704922 R=bradnelson@chromium.org,bbudge@chromium.org Review-Url: https://codereview.chromium.org/2781073003 Cr-Commit-Position: refs/heads/master@{#44255}
-
kozyatinskiy authored
Method should be ready to symbols inside of queue_arr. BUG=v8:6168 R=gsathya@chromium.org Review-Url: https://codereview.chromium.org/2782893003 Cr-Commit-Position: refs/heads/master@{#44254}
-
bjaideep authored
Port 5615e5b8 Original Commit Message: This hopefully shrinks binary size a bit, at the cost of (slightly) increasing the complexity of the ResumeGenerator stub. Includes ia32, x64, mips, mips64, arm and arm64 ports. R=caitp@igalia.com, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG=v8:5855 LOG=N Review-Url: https://codereview.chromium.org/2783043002 Cr-Commit-Position: refs/heads/master@{#44253}
-
thomasanderson authored
This step is no longer necessary after https://codereview.chromium.org/2775913002/ BUG=chromium:705072 Review-Url: https://codereview.chromium.org/2774043002 Cr-Commit-Position: refs/heads/master@{#44252}
-
kozyatinskiy authored
With this CL we don't need to store reference to InspectedContext inside of JavaScript console object and able to get all required information from callback data. It allows us to implement console methods without taking in account how and where we create and store these methods: - later we can move console object implementation to builtins.. - ..and install command line API methods smarter. BUG=chromium:588893 R=dgozman@chromium.org Review-Url: https://codereview.chromium.org/2784713002 Cr-Original-Original-Commit-Position: refs/heads/master@{#44212} Committed: https://chromium.googlesource.com/v8/v8/+/908cd38123df33ce293e4c8d25e407f7ca915f4c Review-Url: https://codereview.chromium.org/2784713002 Cr-Original-Commit-Position: refs/heads/master@{#44238} Committed: https://chromium.googlesource.com/v8/v8/+/88f71126a5c067f98c75044bc26778f2e8ea2e79 Review-Url: https://codereview.chromium.org/2784713002 Cr-Commit-Position: refs/heads/master@{#44251}
-
mtrofin authored
The regression comes from attempting to serialize a module with memory requirements after instantiation - which is what happens in common emscripten scenarios, where the module is obtained from WebAssembly.instantiate(buffer). We then try and serialize the JSArrayBuffer representing the instance memory. That operation fails. Added regression test and also extended the test to cover the other 2 instance-specific values - globals and tables. Added a discussion on WasmCompiledModule (comments) explaining design decisions. BUG=chromium:705562 Review-Url: https://codereview.chromium.org/2784453002 Cr-Commit-Position: refs/heads/master@{#44250}
-
lpy authored
kRuntimeCallStatsTracingEnabled was used as a global flag for runtime stats in tracing, now it is no longer used. TBR=jochen@chromium.org Review-Url: https://codereview.chromium.org/2780293002 Cr-Commit-Position: refs/heads/master@{#44249}
-
Michael Starzinger authored
This removes the debug information (i.e. direct references to the parser source file) from the message, hence making messages consistent between release and debug mode. The debug information can now be printed via the new --trace-asm-parser flag. Also adds two message test cases, showcasing that expected output can now be tested. More tests might be added to the message test suite later whenever it makes sense. R=clemensh@chromium.org BUG=v8:6127 Change-Id: I348044356896442ff9be2d638a564c82fec7a51c Reviewed-on: https://chromium-review.googlesource.com/461942 Commit-Queue: Brad Nelson <bradnelson@chromium.org> Reviewed-by:
-
bjaideep authored
Port bf463c4d Original Commit Message: - Introduce new struct AsyncGeneratorRequest, which holds information pertinent to resuming execution of an AsyncGenerator, such as the Promise associated with the async generator request. It is intended to be used as a singly linked list, and holds a pointer to the next item in te queue. - Introduce JSAsyncGeneratorObject (subclass of JSGeneratorObject), which includes several new internal fields (`queue` which contains a singly linked list of AsyncGeneratorRequest objects, and `await_input` which contains the sent value from an Await expression (This is necessary to prevent function.sent (used by yield*) from having the sent value observably overwritten during execution). - Modify SuspendGenerator to accept a set of Flags, which indicate whether the suspend is for a Yield or Await, and whether it takes place on an async generator or ES6 generator. - Introduce interpreter intrinsics and TF intrinsic lowering for accessing the await input of an async generator - Modify the JSGeneratorStore operator to understand whether or not it's suspending for a normal yield, or an AsyncGenerator Await. This ensures appropriate registers are stored. - Add versions of ResumeGeneratorTrampoline which store the input value in a different field depending on wether it's an AsyncGenerator Await resume, or an ordinary resume. Also modifies whether debug code will assert that the generator object is a JSGeneratorObject or a JSAsyncGeneratorObject depending on the resume type. R=caitp@igalia.com, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com BUG=v8:5855 LOG=N Review-Url: https://codereview.chromium.org/2780283002 Cr-Commit-Position: refs/heads/master@{#44247}
-
