Hi folks, I'm picking up work again on v8:10012 <https://bugs.chromium.org/p/v8/issues/detail?id=10012>. The goal of this work is to regularly build and test V8 for Windows on Arm under Microsoft's Visual C++ Compiler (MSVC), because downstream projects (in particular Node.js) use this compiler.
I've run into a problem with the mkgrokdump utility. Basically, it links with embedded.o (assembled from host_x64/gen/embedded.S), which is generated by the mksnapshot utility. When building with Clang, mksnapshot emits assembly directives compatible with all platforms (and therefore there's no issue). Microsoft's assemblers however don't support this syntax, and there are incompatible differences between the syntax accepted by their i386/x64 assembler and their ARM64 assembler. So mksnapshot emits ARM64 assembly, GN tries to assemble it with the x64 assembler (for linking with mkgrokdump) and and the assembler reports >10000 errors as a result. So based on what I think mkgrokdump does (initialize from the snapshot_blob.bin, enumerate heap constants and export them for another scripts) is there a reason why it has to statically link with embedded.o? Or would it be preferable to keep the build setup as it is and change mksnapshot so it can emit either syntax? Are there more possibilities that we should investigate? I'd appreciate any design input you have on the most workable solution. Best Richard -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/f2e3e89e-ac47-432b-9fb5-00c65350cbfa%40googlegroups.com.
