Anandtech did an in-depth analysis:
Have in mind that SPECint and SPECfp not only measure a single CPU core but also RAM and compiler speed.
I've read that several times and somehow apparently never came to the correct conclusions. Including reservations about RAM (I always struggle to estimate RAM power usage), that still puts the lightning core power usage higher than I expected.
Of course, it goes without saying the cores can and will use less power as more of the system comes on line. A13 clock speeds drop to 2.56GHz when a second CPU core turns on. I'd like to know if they drop further when the GPU cores are fully in use - but one upside of a dual perf core design is that your CPU cores don't become too much of a liability.
Looking again at the Bloomberg design, and assuming now that Apple would need to give 4W a piece to sustain performance equivalent to the iPhone's peak, then an 8 firestorm core part is already demanding 32W for its CPU cores, plus a nominal 2W for four icestorm cores. Apple will invariably want to increase cache sizes for its mac parts, putting further pressure on the APU. Ouch.
That makes pushing clocks higher a nonstarter for the MBP14, which is going to have to pare back watts / clock speeds as more of the APU comes online and may also need a couple firestorm cores lasered off. I think Apple can still get to the point where they can advertise 3GHz (on N5P), but multicore will sustain at lower than that. I also still think it's fine to leave around 12-16 GPU cores on the die - I'd prefer to see an APU with 6 firestorm cores and 16 GPU cores.
The MBP16 is more comfortable throwing 4 or 5W at 8 cores to sustain speeds of up to 3.2GHz on N5P. It can still use the same part as the MBP14, prioritizing good CPU yield and being perfectly happy to disable 4 GPU cores. I'm absolutely against it trying to accommodate all of its GPU needs on a monolithic die now - it needs a separate GPU part, or at a minimum, a separate GPU die.