- 04 Apr, 2019 4 commits
-
-
Tobias Tebbi authored
This changes the syntax for constructing structs and classes to explicitly mention the fieldnames, similar to JavaScript object literals. The fields still have to be listed in the same order as in the struct/class declaration. As in Javascript, {foo: foo} can be abbreviated as {foo}. Example: macro NewJSArray(implicit context: Context)( map: Map, elements: FixedArrayBase): JSArray { return new JSArray{ map, properties_or_hash: kEmptyFixedArray, elements, length: elements.length }; } Drive-by cleanup: Make struct and class constructors follow the same pattern in the parser and the AST. Bug: v8:9018 v8:7793 Change-Id: I22ff7f68270e4f406aa80731a709d41ea52f52bb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1551999Reviewed-by:Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Daniel Clifford <danno@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#60622}
-
Benedikt Meurer authored
Don't record samples from machines without high-resolution timers, as that can cause serious reporting issues. See the thread at http://g/chrome-metrics-team/NwwJEyL8odU/discussion for more details. Bug: v8:9074 Change-Id: I8f9b588b249f944c4bc95feedf56960b28db9ddc Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1552001 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60621}
-
v8-ci-autoroll-builder authored
Rolling v8/test/wasm-js/data: https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+log/8059cd6..2a28a92 [test] Add dedicated test for memory.size (#997) (Andreas Rossberg) https://chromium.googlesource.com/external/github.com/WebAssembly/spec/+/2a28a92 TBR=ahaas@chromium.org,clemensh@chromium.org Change-Id: Idcb9a6f8f57d0e9d3f673d5575e663d729a50366 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1551405Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#60620}
-
Yu Yin authored
This is port for https://crrev.com/c/1524482 Original commit message: This allows immediates to be encoded directly into instructions, rather than mov-ing constants to registers first. This patch only changes emit_{i64,i32}_add, other emit_ functions will be changed once this approach has been approved. Bug: v8:9038 Change-Id: I96929f870e54b24403a32428f3db31b42f41087a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545148Reviewed-by:
Clemens Hammacher <clemensh@chromium.org> Commit-Queue: Yu Yin <xwafish@gmail.com> Cr-Commit-Position: refs/heads/master@{#60619}
-
- 03 Apr, 2019 36 commits
-
-
Adithya Srinivasan authored
This reverts commit 42beed97. Reason for revert: This commit seems to cause consistent failures in some ProcessMemoryMetricsEmitterTest tests on Mac and ChromeOS. I'm not sure what the exact reasoning behind this is. See https://crbug.com/949157. Original change's description: > Reland "[ptr-compr][x64] Temporarily enable pointer compression on x64" > > This is a reland of 4f051fd5 > > Relanding after fixing Chromium issues. > > Original change's description: > > [ptr-compr][x64] Temporarily enable pointer compression on x64 > > > > ... and make sure that the x64 ptr-compr bots proceed testing V8 without > > pointer compression in order to keep testing the full pointer mode. > > > > Bug: v8:7703 > > Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng,v8_linux64_tsan_rel > > Change-Id: Iee725deda813425a6f0722948b54976154f50909 > > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1497139 > > Reviewed-by: Michael Hablich <hablich@chromium.org> > > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > > Commit-Queue: Michael Achenbach <machenbach@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#60230} > > Bug: v8:7703 > Change-Id: Ic2d1c2ae41ec645f34963f5f561c33199c72ef4b > Cq-Include-Trybots: luci.v8.try:v8_linux64_ubsan_rel_ng,v8_linux64_tsan_rel > Cq-Include-Trybots: luci.chromium.try:fuchsia_x64,linux-rel > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535819 > Commit-Queue: Igor Sheludko <ishell@chromium.org> > Reviewed-by: Michael Achenbach <machenbach@chromium.org> > Cr-Commit-Position: refs/heads/master@{#60582} TBR=machenbach@chromium.org,hablich@chromium.org,leszeks@chromium.org,ishell@chromium.org,verwaest@chromium.org Change-Id: Ib9737081e90dddcfe44af9da1275a610da209323 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: v8:7703 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550709 Commit-Queue: Igor Sheludko <ishell@chromium.org> Reviewed-by:
Igor Sheludko <ishell@chromium.org> Cr-Commit-Position: refs/heads/master@{#60618}
-
Dave Tapuska authored
Just rely on calling toString. This matches other vendor's implementations. BUG=chromium:948257 R=dgozman@chromium.org Change-Id: I325a12dd47712263a1ef4deee0bb2de9c4a1c656 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545124Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#60617}
-
Frank Tang authored
Making 43K of room for landing ICU64. Size Change (on x64.release) D8 before 23,683,192 D8 after 23,639,296 Reduce 43,896 bytes Bugs: v8:8348 Change-Id: I057f7d59e955a2e5e017873e5b3b5daf5b142ae2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1478710 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by:
Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#60616}
-
Sathya Gunasekaran authored
These tests make sure the ticks are correct when resolving against a Promise. Without the optimization, the result is: "start,tick 1,tick 2,tick 3,tick 4,done,tick 5" With the optimization, the result is: "start,tick 1,tick 2,done,tick 3,tick 4,tick 5" Bug: v8:8267 Change-Id: I6c6499c7c256927531a99bab4ae1c5bd5069ef7c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1534884Reviewed-by:
Maya Lekova <mslekova@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#60615}
-
Frank Tang authored
Rolling v8/test/test262/data: https://chromium.googlesource.com/external/github.com/tc39/test262/+log/de567d3..324f291 Bug: v8:7834 Change-Id: I31d3ea423078bc14df7cf131f373ba7b661938c8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1544904Reviewed-by:
Sathya Gunasekaran <gsathya@chromium.org> Reviewed-by:
Mathias Bynens <mathias@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#60614}
-
Z Duong Nguyen-Huu authored
This is a part of porting Proxy-related builtins to Torque. Spec: https://tc39.github.io/ecma262/#sec-proxy.revocable Bug: v8:6664 Change-Id: I5f53eb4dff8ff9d3156b601652f3f86ede25fc1d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1529261 Commit-Queue: Z Nguyen-Huu <duongn@microsoft.com> Reviewed-by:
Jakob Gruber <jgruber@chromium.org> Cr-Commit-Position: refs/heads/master@{#60613}
-
Sigurd Schneider authored
Bug: v8:9020 Change-Id: I45f85807132fc9278e90b4cfc7f0dc8326870dfe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1541046 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Toon Verwaest <verwaest@chromium.org> Cr-Commit-Position: refs/heads/master@{#60612}
-
Z Duong Nguyen-Huu authored
Bug: v8:6831 Change-Id: I7d51a49dfbf2e5a1fa2675fe0d70bb4091a4db78 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1544274Reviewed-by:
-
Frederik Gossen authored
Merged WasmCode::Tier into Execution Tier. Bug: v8:9003 Change-Id: I0ad439b8bc060f73e71d60ab9c93dd6bc18d05fe Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547852 Commit-Queue: Frederik Gossen <frgossen@google.com> Reviewed-by:
Michael Starzinger <mstarzinger@chromium.org> Reviewed-by:
-
Clemens Hammacher authored
Even though both are allowed in the style guide, it recommends to use 'using', as its syntax is more consistent with the rest of C++. This CL turns all typedefs in interpreter code to 'using' declarations. R=leszeks@chromium.org Bug: v8:8834 Change-Id: Ide1e8a35a56a840b36b3ceab1307df1bcab94acd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545900Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60609}
-
Clemens Hammacher authored
This CL enables adding code to the top-most {WasmCodeRefScope} when either adding code to the {NativeModule} (we have a nice choke point for that in {PublishCodeLocked}), or when looking up existing code from a {NativeModule}. It also enables the DCHECK that for each such operation, there must be an enclosing {WasmCodeRefScope}. R=titzer@chromium.org Bug: v8:8217 Change-Id: Ie93ca0b31b1577bef074923b3d228a9f214a909c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533861 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by:Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60608}
-
Benedikt Meurer authored
When TurboFan optimizes field access, we need to check first that the runtime already determined the correct field representation properly. If the field representation is still None, we cannot optimize this in TurboFan straight away but we have to call the IC to let the runtime do the magic. Bug: chromium:944865 Change-Id: I032a48824e83806e1be7670346f518b258a9dd65 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549167Reviewed-by:
-
Simon Zünd authored
The native flag is a left-over from self-hosted JavaScript. Currently only the empty function and empty script are marked native. This CL removes the native flag from the ParseInfo, UnoptimizedCompilationInfo and its handling in the bytecode generator. R=leszeks@chromium.org Bug: v8:8834,v8:9043 Change-Id: I60726e28ce83cc84249e9c49bdc88d81f0a695c9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545079Reviewed-by:
-
Clemens Hammacher authored
Using the Isolate's allocator when creating the WasmModule can lead to use-after-free situations when the NativeModule is shared across Isolates. R=mstarzinger@chromium.org Bug: v8:9079 Change-Id: I5a564852179cc5b9d4cbad2a002d3b6e14b01968 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550404Reviewed-by:
-
Benedikt Meurer authored
This adds new timed histograms to measure the time that TurboFan spends on various compilation phases on a per function bases. This includes the following new counters: - V8.TurboFanOptimizePrepare Time spent in the preparation phase of TurboFan optimization. Recorded on each regular optimization of a function. - V8.TurboFanOptimizeExecute Time spent in the execution phase of TurboFan optimization. Recorded on each regular optimization of a function. - V8.TurboFanOptimizeFinalize Time spent in the finalization phase of TurboFan optimization. Recorded on each regular optimization of a function. - V8.TurboFanOptimizeTotalForeground Total time spent on the main thread during TurboFan optimization. Recorded on each regular optimization of a function. - V8.TurboFanOptimizeTotalBackground Total time spent on a background thread during TurboFan optimization. Recorded on each regular optimization of a function. - V8.TurboFanOptimizeTotalTime Total time from starting optimizing to installing the code object. Recorded on each regular optimization of a function. - V8.TurboFanOptimizeForOnStackReplacementPrepare Time spent in the preparation phase of TurboFan optimization for On Stack Replacement (OSR). Recorded on each optimization for on-stack replacement of a function. - V8.TurboFanOptimizeForOnStackReplacementExecute Time spent in the execution phase of TurboFan optimization for On Stack Replacement (OSR). Recorded on each optimization for on-stack replacement of a function. - V8.TurboFanOptimizeForOnStackReplacementFinalize Time spent in the finalization phase of TurboFan optimization for On Stack Replacement (OSR). Recorded on each optimization for on-stack replacement of a function. - V8.TurboFanOptimizeForOnStackReplacementTotalTime Total time from starting optimizing for On Stack Replacement (OSR) to installing the code object. Recorded on each optimization for on-stack replacement of a function. This should give us a good overview and guide/validate future work on the concurrent optimization pipeline. Bug: v8:7790, v8:9074 Change-Id: I96573cd1da472684d06624b7573e4afd6efca99c Doc: http://doc/1umgFxjLQ9p22lVS_BdhmAlo1o9xnxnWlhVi_HMWNktM Cq-Include-Trybots: luci.chromium.try:linux-blink-rel Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547864 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by:
-
Mythri A authored
With lazy feedback allocation we load the interrupt budget from the ClosureFeedbackCellArray instead of the bytecode array. The factory method that constructs the ClosureFeedbackCellArray ensures we have a field for interrupt budget. So, it is safe to omit bounds check here. Including the bounds check increases the size of all jump bytecode handlers by around ~120 bytes. This translates to ~9-10KB of the native code size on Android. Bug: chromium:948835 Change-Id: I8e10b3f630097728ae9e520bfb0d85dfc0f806ea Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550403Reviewed-by:
-
Jaroslav Sevcik authored
On arm processors, we need to have some kind of subexpression elimination running after memory optimizer, so that we reuse index calculation for loads and stores. This CL introduces a small cleanup phase after memory optimizer. Bug: chromium:947225 Change-Id: Ifda7b348d968d58f31947a4ba139863059f4112d Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547664Reviewed-by:
Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Jaroslav Sevcik <jarin@chromium.org> Cr-Commit-Position: refs/heads/master@{#60602}
-
Michael Starzinger authored
This seals any surrounding {HandleScope} when the interpreter enters the main interpreter loop. It ensures that there are no accidental leaks of handles into the surrounding scope and enforces that operations dealing with handles open their own scope. R=clemensh@chromium.org Change-Id: I43d479129bef60beb7565022b24577f8bf1dc522 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550401Reviewed-by: -
Peter Marshall authored
Bug: v8:8834 Change-Id: I1d7451a6306bc34e6254383fd79e8411bffd26ce Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545894Reviewed-by:
-
Clemens Hammacher authored
Reading --verify_predictable makes me sad, whereas --verify-predictable makes me happy. This CL introduces more happiness. R=machenbach@chromium.org Bug: v8:8834 Change-Id: Id51a75f32e6d5a2f87aed81e058a8b6dff189758 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550399Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#60599}
-
Michael Starzinger authored
This adds preliminary support for handling the "br_on_exn" opcode in the interpreter. It also makes "catch" and "rethrow" use a proper exception reference instead of a dummy value. To that end this also adds {Handle<>} as a new kind of {WasmValue} which is intended to pass reference values (e.g. "anyref" or "except_ref") to the runtime system. Therefore lifetime of such a {WasmValue} is directly coupled to any surrounding {HandleScope}. For now we just store {Handle<>} directly on the simulated operand stack of the interpreter. This is of course bogus, since the surrounding scope does not outlive the interpreter activation. Decoupling the lifetime of the operand stack from a {HandleScope} will be done in a follow-up CL. As a drive-by this change also implements support for the "ref_null" and the "ref_is_null" opcodes as a proof-of-concept that the new {WasmValue} is also applicable to the "anyref" reference type. R=clemensh@chromium.org TEST=cctest/test-run-wasm-interpreter/ReferenceTypeLocals BUG=v8:8091,v8:7581 Change-Id: I2307e0689a19c4aab1d67f1ba6742cb3cc31aa3c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1550299 Commit-Queue: Michael Starzinger <mstarzinger@chromium.org> Reviewed-by: -
Daniel Clifford authored
In the process turn the Torque's Arguments type into a real struct and add interoperability with it and CSA's CodeStubArguments. This change is motivated by the desire to include Arguments in structs (e.g. iterators), which is not possible for constexpr fields. Bug: v8:7793 Change-Id: I840538b84c4c58fee75e0b9cd3bdbb3b96a6b948 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549162 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by:
Tobias Tebbi <tebbi@chromium.org> Cr-Commit-Position: refs/heads/master@{#60597}
-
Maciej Goszczycki authored
Bug: v8:8834 Change-Id: Iac747d915f50c64bb91ca7b8365a51d96eacd2ed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549161Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Maciej Goszczycki <goszczycki@google.com> Cr-Commit-Position: refs/heads/master@{#60596}
-
Toon Verwaest authored
- Use IsInRange - Convert scale to index using >>1 which works for 1, 2, 4 - Use mask to check Reads/Writes accumulator Change-Id: Iaeb2236a2d179dc70b62fa599c08984800170336 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1541039 Commit-Queue: Leszek Swirski <leszeks@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Rolling v8/base/trace_event/common: https://chromium.googlesource.com/chromium/src/base/trace_event/common/+log/c69a8ff..ebb658a Rolling v8/build: https://chromium.googlesource.com/chromium/src/build/+log/a72af28..c2f2e5a Rolling v8/third_party/catapult: https://chromium.googlesource.com/catapult/+log/5b63b1f..e1fc0b0 Rolling v8/third_party/depot_tools: https://chromium.googlesource.com/chromium/tools/depot_tools/+log/8d3ba46..865445e Rolling v8/third_party/googletest/src: https://chromium.googlesource.com/external/github.com/google/googletest/+log/a18ac39..b617b27 Rolling v8/tools/clang: https://chromium.googlesource.com/chromium/src/tools/clang/+log/82dbc02..b823d94 TBR=machenbach@chromium.org,hablich@chromium.org,sergiyb@chromium.org Change-Id: If24d37b7a86a73dcb3526e0a75513b0659758aa7 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549791Reviewed-by:
-
Clemens Hammacher authored
During instantiation, exceptions can be thrown when looking up the imports, e.g. because of proxies. If the exception is thrown internally, before actually calling out to JS code, it won't be externally caught. This CL removes the DCHECK that errornously checked that a pending exception was externally caught. R=mstarzinger@chromium.org Bug: chromium:948228 Change-Id: Idbdb340167c1943f78397cc9b310ef5743755726 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547855Reviewed-by:
-
Daniel Clifford authored
Const-qualified fields are allowed in both classes and structs. In both cases, const fields can only be set via initialization during construction. Drive-by: unitialized -> uninitialized Bug: v8:7793 Change-Id: Idec08df30f7897c756b7dd6f2b10bb6012fefb6a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547853 Commit-Queue: Daniel Clifford <danno@chromium.org> Reviewed-by:
-
Frederik Gossen authored
The tiers are now consistently referred to as baselin and top tier. Bug: v8:9003 Change-Id: I74ad1867aca63bee9eb83b7f0f9fbaf2b1523dcb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547667 Commit-Queue: Frederik Gossen <frgossen@google.com> Reviewed-by:
-
Andrew Comminos authored
Adds the notion of a "source type" to CpuProfileNode instances, hinting at the underlying source of the function or state that resulted in the generation of the node. Bug: v8:9001 Change-Id: Ie14c54d41b99eb02f54b423fa5d939e9d7f63785 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1510576 Commit-Queue: Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Peter Marshall <petermarshall@chromium.org> Reviewed-by:
Alexei Filippov <alph@chromium.org> Cr-Commit-Position: refs/heads/master@{#60590}
-
Sigurd Schneider authored
This CL uses MemCopy in CopyElements, because we think that the input FixedArrays can never overlap. This CL also adds a DCHECK to ensure this. If our assumption is wrong, it will be interesting to learn why. Change-Id: Ib8258b934f43b82b1281481c592762e43b35938f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549154 Commit-Queue: Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Hannes Payer <hpayer@chromium.org> Cr-Commit-Position: refs/heads/master@{#60589}
-
Clemens Hammacher authored
The cache also needs to keep the code alive. The code objects are import wrappers and not wasm functions (which we will focus on first), but eventually we would also like to collect unused import wrappers. This CL explicitly increments the ref count when {WasmCode} is added to the cache, and derements all ref counts in the destructor. R=titzer@chromium.org Bug: v8:8217 Change-Id: I1bfb276b25b359d83900147e75ec47788e1fa8de Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1535825Reviewed-by: -
Santiago Aboy Solanes authored
Includes both changing from compressed pointers and to compressed pointers. Also added tests to the representation changer test B Cq-Include-Trybots: luci.v8.try:v8_linux64_pointer_compression_rel_ng,v8_linux64_arm64_pointer_compression_rel_ng Bug: v8:8977 Change-Id: I8a13f6b7ec2208442aa354949173cc9061bce168 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1533866Reviewed-by:
-
Michael Starzinger authored
This introduces a helper class for the immediates to a "br_on_exn" instruction. It is basically a wrapper around a pair of existing immediates to simplify PC offset calculations. This is similar to what is being done for e.g. {MemoryCopyImmediate} already. R=clemensh@chromium.org BUG=v8:8091 Change-Id: I85a552baa6bfa78304abc6cf9509aef365d47057 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547865Reviewed-by: -
Clemens Hammacher authored
Even though both are allowed in the style guide, it recommends to use 'using', as its syntax is more consistent with the rest of C++. This CL turns all typedefs in src/regexp to 'using' declarations. R=jgruber@chromium.org Bug: v8:8834 Change-Id: I2765c3465fec7e8c42c3a84b924522f220ab5676 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1545904Reviewed-by:
-
Clemens Hammacher authored
All standard containers provide a method named {empty} to check whether the container is empty. On {base::Vector}, that method is named {is_empty}, while {empty} is an unused factory method for creating an empty {Vector}. This CL renames {is_empty} to {empty} and removes the unused factory method. R=leszeks@chromium.org Bug: v8:8834 Change-Id: I686bd07527801fbe783c412bc241221d8ec3660a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1547862 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: -
Michael Lippautz authored
They are already filtered by the incremental marker. Change-Id: If43a16d54a2b0eb7d6a36482d3439fc7191c31a6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1549160 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
-
