2 ms·
Yeah, vertical microcode always looked pretty RISCy if you're not used to it. And FWIW, I've heard that there's two distinct uOp formats inside a.single core t
by monocasa 7y ago
Yeah, vertical microcode always looked pretty RISCy if you're not used to it.
And FWIW, I've heard that there's two distinct uOp formats inside a.single core these days for quite a few of the uArchs. There's the frontends view which is concerned with amortizing decode costs (so wide fixed purpose instructions, that other wise look pretty CISC), and the backend's uOps that's concerned with work scheduled on functional units. A lot of the fusion happens on the front end, and a lot of the cracking happens on the backend, and the frotbejd tends to be two address, and the backend three address. So like a frontend's
and rax, [rbx, addr]
is something like
ld_agu t0, rbx, addr
ld t1, t0
and rax, rax, t1
on the backend.