Phoenix doesn't have the bug?
Phoenix does not have the SGPR bug but it has the export conflict bug.
Seems all current RDNA3 chips have this export conflict bug. I understood it can impact performance in no insignificant amount. By how much? we will never know.
There definitely something wrong with clocks, just compare RDNA3 vs Zen4
Obviously Zen 4 is on a performance optimized library.
Zen 4 density is 92 MTr/mm2. N31 GCD is 132.4 MTr/mm2.
For comparison, RDNA2 and Zen 3/Vermeer have performance optimized libraries, both are at ~51 MTr/mm2.
I am doubtful if there is really an issue with the usage of high density libraries. It is a conscious decision which means they know what they are going to get if they use HD libs.
RDNA3 performance is fine, relative to Lovelace.
They just don't have enough silicon on N31 to compete at the very top. It is a conscious choice.
And if they really put "Architected to exceed 3 GHz" then it has to be so, btw this is also the same thing which the press have been briefed.
You can see Jarred Walton slipping on this NDA'd info in someone's livestream.
BTW, it is not like they are making the patches right now and discovered oopsies, lots of patches were from last year if you check the initial commits which were not squashed.
Drivers development usually starts long before the chip is even taped out. They directly push the RTL code to the emulator and start writing drivers. The physical implementation goes in parallel.
Some HW bugs are just not deemed significant enough to warrant an architecture rework.
Minor physical implementation bugs sometimes can be fixed with metal layers. Many new blocks have unused silicon around critical areas to change logic in case of bugs. The metal layers can be adapted to form a corrective logic with the additional unused transistors.
Then there are chicken bits, which gets fused off in case things don't work the way they are intended. GPUs have tons of chicken bits.