For a fixed length move, none. For a variable length move, one. Sent from my iPhone
> On Apr 15, 2022, at 12:27 PM, Robin Vowels <[email protected]> wrote: > > On 2022-04-16 02:23, Tom Harper wrote: >>>> On Apr 15, 2022, at 12:20 PM, Robin Vowels <[email protected]> wrote: >>> On 2022-04-16 00:25, Tom Harper wrote: >>>> Well known. But the instruction I’m proposing has no registers >>>> involved >>> Oh? How do you propose that such an instruction move >>> N bytes (where N is variable) without the value of N >>> being in a register? >> As mentioned, R0. > > Make up your mind! You just said that no registers were involved. > >>>> (other than base displacement) and thus there is no way to >>>> restart the instruction to complete the process. >>>> So to avoid that, limiting it to 256 bytes removed that as an issue. >>>>>> On Apr 15, 2022, at 9:45 AM, Seymour J Metz <[email protected]> wrote: >>>>> You can have interruptability without an arbitrary length restriction; >>>>> CLCL and MVCL work just fine. All that you need is that the instruction >>>>> be resumeable and for the hardware/microcode/millicode to periodically >>>>> check for pending interrupts and update the registers as needed -------------------------------------------------------------------------------- This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use.
