*TLDR: we are planning to remove support for nosnapshot builds (gn flag: 'v8_use_snapshot = false') and builds without embedded builtins (gn flag: 'v8_enable_embedded_builtins = false').*
*Snapshot?* Currently, V8 supports building with- and without a snapshot <https://v8.dev/blog/custom-startup-snapshots>. In nosnapshot builds each isolate is created from scratch while snapshot builds deserialize the initial heap state from snapshot_blob.bin. *Embedded builtins?* V8's builtin code objects used to be part of the initial heap state. With the recent addition of embedded builtins <https://v8.dev/blog/embedded-builtins>, builtin code objects can now be compiled into the V8 binary instead. *What will change* We are planning to 1. remove support for nosnapshot builds, and 2. remove support for builds without embedded builtins (noembed builds). nosnapshot and noembed builds should be considered deprecated as of V8 7.4. They are subject to removal in 7.5 onwards. Embedders will need to update any custom build processes to use embedded builtins. Specifically, mksnapshot now generates an assembly file (pass --embedded_src <filename>) that is later compiled into the V8 binary. See V8's BUILD.gn <https://cs.chromium.org/chromium/src/v8/BUILD.gn?l=1079&rcl=fee9be7abb565fc2f2ae7c20e7597bece4fc7144> file for an example. Note that mksnapshot must thus run prior to compilation of the V8 binary. Due to dependencies between the snapshot blob and embedded builtins, it is strongly recommended to generate both in the same mksnapshot run. -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
