This is the mail archive of the
mailing list for the GCC project.
Re: Register constraints + and =
> I thought that the "operand" in a mem:BLK is the pointer to the block,
> not the block itself. So if the instruction(s) generated don't touch
> the pointer -- a likely answer for a block-move instruction -- then
> the operand would be read-only. Is that the right interpretation?
But many block move instructions do in fact touch the pointer, in that
they update the registers pointing to the starts of the blocks to point
to the ends after the instruction completes.