Algorithms for Modern Processor Architectures

I don't think talks are being recorded, unfortunately.

JavaScript does, so the web does, so by extension Apple probably does care about utf16.

is this talk about apple? Regardless, lots of language runtimes still use utf16 (eg java, qt, haskell), and windows certainly still uses utf16.

The Pentium 3 is what eventually topped out at 1.4 GHz, for the 130nm Tualatin parts introduced in 2001. The Pentium 4 started at 1.4GHz and 1.5GHz with the 180nm Willamette parts introduced in 2000. Those were eventually released with speeds up to 2.0GHz. The 130nm Pentium 4 Northwood reached 3.4GHz in 2004, and the 90nm Pentium 4 Prescott hit 3.8GHz later in 2004.

Intel released a couple of Pentium 4's from different cores topping at 3.8GHz [0].

Tom's Hardware overclocked one of these Northwood Pentium 4's to 5 GHz with liquid nitrogen and a compressor [1].

Those were the days, honestly.

[0]: https://en.wikipedia.org/wiki/Pentium_4

[1]: https://www.youtube.com/watch?v=z0jQZxH7NgM

The Pentium 4 HT 670, released in 2005, came factory-clocked at 3.8 (https://www.techpowerup.com/cpu-specs/pentium-4-ht-670.c20)

Netburst lasted a long time as intel was floundering, before Core Duo was released in 2006.

Both LLVM and GCC is being supported by processor manufacturers directly. Yes, Apple and Intel has their own LLVM versions, but as long as don't break compatibility with GCC and doesn't prevent porting explicitly, I don't see a problem.

I personally use GCC suite exclusively though, and while LLVM is not my favorite compiler, we can thank them for spurring GCC team into action for improving their game.

Can you be more explicit? Is it because they are optimizing too much to a single platform that isn't generalizable to other compilers or architectures? What's your specific gripe?

Whose hands exactly is LLVM in?

Also to be more controversial. - redhat deprecated x86_64_v1 & x86_64v2 . and people were crying because of that....