3 ms·
uOPs are proprietary and undocumented: potentially changing between architectures even from the same company. So it's hard to generalize. But it's my understan
by dragontamer 6y ago
uOPs are proprietary and undocumented: potentially changing between architectures even from the same company. So it's hard to generalize.
But it's my understanding that uOPs are constant sized. Having a variable length uOP seems counterproductive. If something is so complex that it won't fit in one uOP, then it's probably preferable to encode it as two separate uOPs.
We can get an idea of what is multiple uOPs by looking at the pipelines and latency charts. But even then: multiplication is likely one uOP despite taking multiple clock ticks of latency. So it's not exactly a precise science...
- gpderetta 6y agoThe number of uops for each instruction is well documented. IIRC uops can take more than one solt in the uop cache if they need to encode large constants, so they are technically variable length.
- mhh__ 6y agoWe know - and your compiler knows - exactly how many uOps are generated and which ports they execute on them - just not what they really do. Intel's performance counters can be fairly elucidating as to what your computer is doing - but - finding one you actually want can often mean scrolling through a list of thousands. My point is that small code is useful - unrolling a twice nested loop can kill performance if you aren't careful.