OpenCL might not have existed but it is still possible to encounter a CPU, chipset, and GPU load situation nonetheless.
Yes, and that would involve adding expense and noise to a machine for purely theoretical reasons.
I suspect quite the opposite occurred. I suspect that Apple designed to a predicted thermal envelope, then during testing discovered that it got too hot. Then, *after testing*, they underclocked the graphics to avoid the problem.
I also seem to remember at least one case where Apple slowed the GPU clock even more in a firmware update to "fix" a problem in the field.
I stand by my firm belief that it is possible that my speculation is somewhat related to the facts.
I also believe in the rule that with computer hardware and software
things which aren't tested do not work. Apple's laptops and laptops-on-sticks have a history of heat-related issues running previous applications. I don't find it unreasonable to have suspicions that OpenCL and H.264 acceleration could be a problem.
(below)
OpenCL and h.264 decoding are a problem but gaming or encoding isn't?
The point is that usually
things which aren't tested do not work.
OpenCL and encoding would definitely involve streaming multiple threads of work to the GPU for extended lengths of time.
Decoding would be fairly simple compared to encoding - Windows has been using hardware assisted decoding for years without any noticeable issues.
Let me repeat again that I'm merely speculating that the new features may cause some models to go outside their thermal design envelope, and Apple may have decided to exclude them from the "supported" list even though the chips are capable.
I'm ending the back-and-forth on this topic, no point to drag it out more. (But I'll bookmark this thread just in case after 10.6 ships there are reports of overheating Macs

)