3 ms·
Not _is_, but. _may_be_. At least that's what I read. My question is why would they spend effort (and it is an effort; they would have to add logic to not set
by Someone 9y ago
Not _is_, but. _may_be_. At least that's what I read.
My question is why would they spend effort (and it is an effort; they would have to add logic to not set carry/overflow/zero flags when writing results to that register, for example) making that a no-op if no sane programmer would use them?
- rbanffy 9y agoSorry. I was thinking about stores. Other instructions may cause side effects that could be hard to avoid. It's fine to keep some behaviors of the ISA undefined. Different implementations may act differently. One generation may really avoid any side effects by retiring the instruction during the decoding stage while a simpler, say, low-power implementation may leave some side-effects (a carry that was set during an addition while the result is ignored). Stating that it may be ignored keeps the implementations free to do whatever is more convenient.