We don't use this at runtime either. The compile time is horrible, and v8's binary size will grow up dramatically. But we do try it for wasm. And make the binary performance close to the clang version.
在 2019年11月27日星期三 UTC+8下午10:53:13，mvst...@google.com写道： > > Hi, I've created a tracking bug on which we'll apply some more > investigation (https://bugs.chromium.org/p/v8/issues/detail?id=10023). > We'll have a detailed look in January. Are you interested in upstreaming > your work? We're interested in using this for the built-ins and interpreter > bytecode handlers, as part of the mksnapshot build step. We wouldn't try to > do this at runtime. > > All the best, > --Michael Stanton > --V8 Compiler Team, Manager > > On Tuesday, November 26, 2019 at 2:35:39 AM UTC+1, manji...@gmail.com > wrote: >> >> >> You may test the arm-6-9 branch first. The performance data show above >> comes from this branch. And it is so stable that it survived alibaba's >> 11.11. >> > -- -- v8-dev mailing list v8-dev@googlegroups.com 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 v8-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/bd340f92-63af-4e3e-b217-55a9ff0db1e6%40googlegroups.com.
