> Ah, so you don't actually care about V8's compilers To be more precise: I want to profile V8`s compilers, esp. in terms of how they themselves have been compiled [for the confused reader: by GCC/Clang/etc.].
> Could have said so :-) I didn`t want to be insulting to the V8 community. ;-) > turning those into a benchmark will require hackery That`s what I was afraid of. :-( > and will not be representative of production use. Of course not. > Maybe you don't require purity. Not really. > The easiest approach would be to run some workload that just so happens to > spend a lot of time in C++ code. > For example, Octane's "Code-load" test spends 98% of its time in C++ > (about 75% in parser and full-codegen, less than 1% in optimizing compilers). Thanks, but I found the preceding to be confusing. I _do_ want to spend lots of time [relatively speaking] in "optimizing compilers"; ideally, I want to profile Crankshaft and/or TurboFan withOUT running the code they compiled. Yes, I know that w/o type feedback the compiled code will essentially be crap from a real-world-performance POV. For the purposes of _this_ mini-project, I don`t care about that. Thanks again. Regards, Abe -- -- 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.
