512 * 64 = 32 kB. 512 is 8 * 8 * 8, I'd guess if they add more (up to 4096) L1 cache lines that access would take 1 clock longer. Which is very likely a net performance loss.
Maybe it's time to increase cache line size to 128 bytes. That could of course break a lot of old code performance wise. It'd cause more false sharing [1] and double memory bandwidth requirements for random access. Maybe we should start to organize shared data to have 128 byte alignment.
It'd also break some read bandwidth-saving code that assumes 64 byte streaming (non-temporal) stores eliminate need for RFO [2] access.
Writing a single byte to RAM would require CPU core to first read a 128 byte cache line (RFO [2]) and then eventually write that cache line back. Currently "only" 64 bytes need to be read and written in the same scenario.
128 byte cache lines would mean L1C and L1D caches are both 64 kB, up from current 32 kB. That'd definitely help with monstrous codebases.
CPU design is full of compromises...
[1]: Atomic ops unintentionally touching same cache line cause performance loss through false sharing. The effect can be very significant, up to 2 orders of magnitude. https://en.wikipedia.org/wiki/False_sharing
[2]: Read for Ownership. https://en.wikipedia.org/wiki/MESI_protocol#Read_For_Ownersh...