> If you give gcc the appropriate 'march' parameter it can use vectorisation automatically if it figures out it can do it. Yes, I'm aware of loop vectorization

> If you give gcc the appropriate 'march' parameter it can use vectorisation automatically if it figures out it can do it. Yes, I'm aware of loop vectorization in C compilers. I'm also aware of loop vectorization in Java JIT compilers. Do you think there is anything specific to C or C++ that makes this easier than in Java? There isn't. > The main argument here is that native languages let you get the most out of your CPU if you want Most applications, including probably more than 99% of Chromium, are not the kind of code that would benefit from manually written vector intrinsics. Does the "main argument" claim that these 99% would also be 5x or 10x slower if they were written in Java?