www-client/chromium is missing system-v8 use flag, which would allow to use statically linked v8, which is used by www-client/google-chrome Statically linked libraries can be faster than dynamically linked. Sunspider is 7% slower in chromium than in google-chrome.
Without custom-cflags Sunspider 0.9.1 is 12% slower on Chromium 25.0.1364.45 Chrome 175.9ms Chromium 196.3ms
tried to disable system v8 by removing all occurrences of v8 from ebuild but it fails to build make: *** No rule to make target `out/Release/obj.target/v8_base/v8/src/accessors.o', needed by `out/Release/obj.target/v8/tools/gyp/libv8_base.a'. Stop. make: *** Waiting for unfinished jobs....
We're going to continue using system v8. Your benchmark results have possibly more to do with the way we compile dev-lang/v8 than the dynamic linking. After startup speed should be the same. Feel free to file a separate bug after figuring out why exactly the slowdown occurs.
Statically linked libraries are sometimes faster than dynamically linked. app-benchmarks/nbench FOURIER is 6% faster when linked statically. with -static FOURIER : 44168 : 50.23 : 28.21 without -static FOURIER : 41752 : 47.48 : 26.67 Do you know why chromium doesn't build without system v8?
I believe we remove the v8 source files in src_prepare. Or possibly the chromium-lite tarballs do not include it.
*** Bug 454720 has been marked as a duplicate of this bug. ***
