Re:“Coding is basically just ifs and for loops.”
by rzzzt on Saturday December 04, 2021 @05:26PM
(#29444868)
Oh, but CPU instructions can be built up from a series of μops which are then executed out of order or in an overlapping fashion, making both "instruction" and "state" boundaries in your equation more fuzzy than it looks. So at the absolute-absolute bottom of "code", it is instructions for an abstract model of an interpretative device.
[ Parent
| on HN ]
Re:“Coding is basically just ifs and for loops.”
by reikonomusha on Saturday December 04, 2021 @05:32PM
(#29444918)
(I'm not sure if your "but" is a retort, or an addendum. Assuming retort...) We can consider one more level of implementation machinery, but I fail to understand how uops aren't another form of instruction, and CPU internal gobbledygook like register files, caches, etc. aren't another form of state. It doesn't seem so fuzzy.
Re:“Coding is basically just ifs and for loops.”
by rzzzt on Saturday December 04, 2021 @05:56PM
(#29445069)
The difference is that you don't get to access the uops machine, subsets/sequences of that instruction set are offered as (macro-)instructions instead. Programming happens on the idea of a CPU.
Re:“Coding is basically just ifs and for loops.”
by valenterry on Sunday December 05, 2021 @01:05AM
(#29447154)
> Oh, but CPU instructions ...
And who says your code runs on a CPU? :^)