| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Remove special handling for side-effect check in ArrayPrototypeFill The special handling with explicit side effect check is not necessary, since we have a general mechanism via Debug::PerformSideEffectCheckForObject. Also added a test to make sure Array.prototype.fill triggers side effects for an existing array but does not for a newly-created array. R=syg@chormium.org Change-Id: I44a82823bd35bee9a900468832c3e79c3d15a121 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4624438 Reviewed-by: Shu-yu Guo <syg@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/main@{#88399} | 3 年前 | |
Mark intrinsics AsyncFunction{Enter,Reject,Resolve} as side-effect free This fixes the DevTools console preview when using REPL mode. AsyncFunction* intriniscs are side-effect free and marking them as such is correct. Bug: chromium:1043151 Change-Id: Ie0c36507b98b0c12f3d627c34102c04c27358ff2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2010106 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Simon Zünd <szuend@chromium.org> Cr-Commit-Position: refs/heads/master@{#65876} | 6 年前 | |
[temporal] Remove --harmony-temporal from non-Temporal tests In https://chromium-review.googlesource.com/c/v8/v8/+/7111926 I added --harmony-temporal to some tests to ensure they still pass with Temporal enabled. However, they are not Temporal tests; they should not be enabling this flag long term. Now that Temporal is unflagged (https://chromium-review.googlesource.com/c/v8/v8/+/7123876), this can be removed. Bug: 401065166 Change-Id: I00a7f7d585670bd0ddc10501931add682e803cfc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7124594 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Auto-Submit: Manish Goregaokar <manishearth@google.com> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#103562} | 8 个月前 | |
[tests] Clean up flags for staged JS features Bug: 391658080 Change-Id: Ib68e18d2f3c31e39236e019ebcdd91701ed6653c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6199809 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#98370} | 1 年前 | |
[debug] allow calls to some builtins on temporary objects This CL allows SetPrototypeAdd and ArrayIteratorPrototypeNext to be called on temporary objects during side effect free evaluation. Bug: v8:7588 Change-Id: Id77848e48d98c243de91bc6c0fae5a0877e693d4 Reviewed-on: https://chromium-review.googlesource.com/998439 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#52548} | 8 年前 | |
[debug] move side-effect tests into subfolder Bug: chromium:810176 Change-Id: I089a1678dfbe0c3bb664e54818a6853f66d364b2 Reviewed-on: https://chromium-review.googlesource.com/923387 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#51347} | 8 年前 | |
[debug] allow calls to some builtins on temporary objects This CL allows SetPrototypeAdd and ArrayIteratorPrototypeNext to be called on temporary objects during side effect free evaluation. Bug: v8:7588 Change-Id: Id77848e48d98c243de91bc6c0fae5a0877e693d4 Reviewed-on: https://chromium-review.googlesource.com/998439 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#52548} | 8 年前 | |
[debugger] allow some map, set, regexp and array builtins on tmp objects.. .. for side effect free debug evaluate. R=yangguo@chromium.org Bug: v8:7588 Change-Id: Iac4d782dbf996d9c11430fc681f38a648d89435b Reviewed-on: https://chromium-review.googlesource.com/1000527 Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#52699} | 8 年前 | |
Reland "[contexts] Unify context accessors after ContextCells" This is a reland of commit d2ab66c2a942893b9f6d7628ff8892e1d6a607b3 Changes from original: - The test inspector/debugger/set-breakpoint-after-gc relies on precise garbage collection and may fail if conservative stack scanning is used. We call GC multiple times to ensure the weak reference hold by the script is eventually collected. - Allow reading a ContextCell when printing debug stack frame. Original change's description: > [contexts] Unify context accessors after ContextCells > > The introduction of ContextCells removed the need for special handling > for ScriptContext (which previously used a side table for > let/const tracking and mutable numbers). > > This change refactors the context access logic: > - Internal get/set accessors are now protected to the Context class. > - External access should use the new functions: > - Get/Set: A safe (though potentially slower) > function for accessing elements in any context. > - GetNoCell/SetNoCell: A faster function that verifies the > element being accessed is not a ContextCell. > > Additionally, related bytecode operations and optimizer functions have > been renamed for consistency with these changes. > > Bug: 408128754 > > Change-Id: I785281ab6f13b0ae65578eb5d2f0a5750457ab5e > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6450582 > Reviewed-by: Igor Sheludko <ishell@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Commit-Queue: Victor Gomes <victorgomes@chromium.org> > Cr-Commit-Position: refs/heads/main@{#99844} Bug: 408128754, 40789559 Change-Id: I78a3a99a4f364ed78965fbed56a084d38382d2fc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6479814 Reviewed-by: Igor Sheludko <ishell@chromium.org> Auto-Submit: Victor Gomes <victorgomes@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#99865} | 1 年前 | |
[error] Define Error.stack property as a JavaScript accessor ... instead of the native data property. This fixes the JS spec violation when reading a data property does not expect any observable side effects. For example, OrdinaryGetOwnProperty (see https://tc39.es/ecma262/#sec-ordinarygetownproperty, step 4a). Differences to previous behaviour: - Error.stack is defined as a JavaScript accessor property. - all Error objects get a private "error_stack_symbol" field where the captured stack trace is stored (previously it was added only when the error was actually thrown which caused unnecessary transitions). - Error.captureStackTrace(obj) adds public "stack" accessor property and private "error_stack_symbol" property to given "obj". - calling "stack" getter/setter is a no-op in case receiver is not an "Error-like" object, i.e. it doesn't have a "error_stack_symbol" property and it doesn't have a prototype with such a property (the lookup stops at JSProxy or interceptor). - the "stack" getter walks the prototype chain from receiver until it finds a holder with the "error_stack_symbol" property which is then used for computing the result. This is slightly different from the previous behaviour in case receiver's prototype chain contains multiple error objects. - the "stack" setter walks the prototype chain from receiver until it finds a holder with the "error_stack_symbol" property and stores the value there. Drive-by: handle lazy accessor pairs in ObjectVisitorDeepFreezer. Bug: v8:5962 Change-Id: I109d6fbbbdb9588d13ca86d217efd9a4a11d8447 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4459251 Reviewed-by: Toon Verwaest <verwaest@chromium.org> Reviewed-by: Shu-yu Guo <syg@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/main@{#87286} | 3 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 年前 | ||
| 6 年前 | ||
| 8 个月前 | ||
| 1 年前 | ||
| 8 年前 | ||
| 8 年前 | ||
| 8 年前 | ||
| 8 年前 | ||
| 1 年前 | ||
| 3 年前 |