• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Discussion Qualcomm Snapdragon Thread

Page 31 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Look also at how low Qualcomm can go for platform power in ST — at a reduced but still functional performance of about 1/3 of each peak ST, Qualcomm can drop down to 2W whereas AMD/Intel are at around 5. Telling about the fabrics of each and the scalability of the core.

QC may not have real E cores this round but I bet the battery life will still be great.
 
Yep, they don't need an e core to fight MTL and Zen 4.
They need it to fight Apple, indirectly, in phones.
No, they'll need it next generation even to fight AMD/Intel.

AMD is set to make a colossal leap in their P-core power efficiency with Zen 5. And Intel is finally getting rid of their node disadvantage, and pursuing E-cores.
 
Look also at how low Qualcomm can go for platform power in ST — at a reduced but still functional performance of about 1/3 of each peak ST, Qualcomm can drop down to 2W whereas AMD/Intel are at around 5. Telling about the fabrics of each and the scalability of the core.

QC may not have real E cores this round but I bet the battery life will still be great.
As good as Zen 5 (Strix Point) might be, it won't beat X Elite in this aspect. Even Adroc has admitted that X Elite will have fabric/idle power advantage.
 
Look also at how low Qualcomm can go for platform power in ST — at a reduced but still functional performance of about 1/3 of each peak ST, Qualcomm can drop down to 2W whereas AMD/Intel are at around 5. Telling about the fabrics of each and the scalability of the core.

QC may not have real E cores this round but I bet the battery life will still be great.

Skip to 13:00

Gerard Williams talks about the X Elite having only performance cores, and no efficiency cores.
 
20240401_124905.jpg
I am kinda disappointed with the graphics of X Elite.

M2/M3 level of performance at M2 Pro/M3 Pro levels of power consumption.

I want them to beat the base M chip's graphics performance, while having similar efficiency.

We know Qualcomm can do it. Their Adreno is the leader in mobile GPUs.

The reason the X Elite lags behind M2/M3's GPU efficiency is probably because they did not allocate sufficient transistor budget to it. It explains how they achieved the miniscule ~170 mm² die size.

X Elite's GPU efficiency right now is good enough to beat Meteor Lake and Hawk Point, but I suspect next gen Lunar Lake and Stric Point might probably beat it. But it's certainly nowhere at Apple's level.

The impressive thing about Apple Silicon is every part of it is efficient. Not just the CPU (which is most talked about), but also the GPU, NPU, Media Engine, display engines, thunderbolt ports etc.... Apple is willing to splurge with regards to the transistor budget. A single Apple Thunderbolt controller in an M chip takes up as much area as a CPU P-core!

I wish future Snapdragon X processors would actually splurge on the GPU transistor budget, so we can do some actual power efficient gaming on it, and it would make it fit to put in tablets.

However, looking at the rumour mill, it sounds rather grim. Revegnus (in one of his last leaks), said X Elite Gen 2 will use an overclocked Adreno 830 GPU.

FWIW, Adreno 830 is the GPU powering the upcoming Snapdragon 8 Gen 4. It is 10% faster than M2's GPU, and the same performance as the GPU in the X Elite 80W TDP.

Screenshot_20231105_195431_YouTube.jpg
 
Last edited:
And ARM added instruction(s) which match JavaScript behavior to enable faster JITs: https://developer.arm.com/documentation/dui0801/h/A64-Floating-point-Instructions/FJCVTZS

With all its complexity is there even a single x64 instruction to do that? cvttsd2siq is close but still compare the implementations of TruncateDoubleToI in the arm64 and x64 macroassemblers in V8. A feature check and a single instruction vs all that crap. They just aren't innovating at the same rate.
 
Last edited:
And ARM added instruction(s) which match JavaScript behavior to enable faster JITs: https://developer.arm.com/documentation/dui0801/h/A64-Floating-point-Instructions/FJCVTZS

With all its complexity is there even a single x64 instruction to do that? cvttsd2siq is close but still compare the implementations of TruncateDoubleToI in the arm64 and x64 macroassemblers in V8. A feature check and a single instruction vs all that crap. They just aren't innovating at the same rate.
I thought JavaScript has this behaviour because that's how it works by default on x86? Is this not just replicating some old SSE truncate behaviour?
 
I thought JavaScript has this behaviour because that's how it works by default on x86? Is this not just replicating some old SSE truncate behaviour?
It's close to cvttsd2siq but x64 version ends up being more instructions. At least 4 including an often untaken branch.

Although it was much worse on ARM before that which is probably why they added it.

Also to be clear I have no idea about assembly I just want faster JavaScript engines.
 
Last edited:
It's close to cvttsd2siq but x64 version ends up being more instructions. At least 4 including an often untaken branch.

Although it was much worse on ARM before that which is probably why they added it.
Gory details:
 
And ARM added instruction(s) which match JavaScript behavior to enable faster JITs: https://developer.arm.com/documentation/dui0801/h/A64-Floating-point-Instructions/FJCVTZS

With all its complexity is there even a single x64 instruction to do that? cvttsd2siq is close but still compare the implementations of TruncateDoubleToI in the arm64 and x64 macroassemblers in V8. A feature check and a single instruction vs all that crap. They just aren't innovating at the same rate.
Ooh. Very interesting.
 
Ooh. Very interesting.
No. Not really. I smell Google. They stand to gain the most from performant Javascript. They want you to never leave ChromeOS or Android or Gmail or Google Docs. You wanna know how often I have to kill a Win32 process due to errant behavior consuming too much CPU? Almost never. How often do I kill a tab in a browser due to errant JS script eating CPU cycles? Almost every day.
 
No. Not really. I smell Google. They stand to gain the most from performant Javascript. They want you to never leave ChromeOS or Android or Gmail or Google Docs. You wanna know how often I have to kill a Win32 process due to errant behavior consuming too much CPU? Almost never. How often do I kill a tab in a browser due to errant JS script eating CPU cycles? Almost every day.
This also happens with Firefox 😉
Browsers and their JS engines have become part of the most complex software stacks.
 
Yeah but that doesn't explain the low 2400 ST score. Qualcomm has shown that X Elite can do 2700 in a 23W device TDP envelope.

So this Lenovo device is either a <10W fanless device or a fanned laptop but still in testing/debugging phase.
We really need independent reviews.
Btw why doesn't this thread have the functionality of upvoting/downvoting comments?
So it was you doing that. Those arrows are not for what you think they are for FYI.

Olrak wants an Android tablet with X Elite
To be fair, the one thing that could pry me away from my iPad would be a 7” tablet with the x elite running Android so I agree with him.
 
Isn't the 8G4 basically a Phoenix for Phones with the 2P + 6E Phoenix Cores. While also having the latest updated IPs from QCOM, specially the shiny new Adreno 8 series uArch?

I don't see much reason for X Elite on the Android space due to this.
 
Back
Top