diff options
Diffstat (limited to 'gcc/md.texi')
| -rw-r--r-- | gcc/md.texi | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/gcc/md.texi b/gcc/md.texi index ab89816..acc616f 100644 --- a/gcc/md.texi +++ b/gcc/md.texi @@ -1735,23 +1735,23 @@ scratch registers after reload, you must define patterns @samp{reload_in@var{m}} or @samp{reload_out@var{m}} to handle them. @xref{Register Classes}. -The constraints on a @samp{move@var{m}} must permit moving any hard +The constraints on a @samp{mov@var{m}} must permit moving any hard register to any other hard register provided that @code{HARD_REGNO_MODE_OK} permits mode @var{m} in both registers and @code{REGISTER_MOVE_COST} applied to their classes returns a value of 2. -It is obligatory to support floating point @samp{move@var{m}} +It is obligatory to support floating point @samp{mov@var{m}} instructions into and out of any registers that can hold fixed point values, because unions and structures (which have modes @code{SImode} or @code{DImode}) can be in those registers and they may have floating point members. -There may also be a need to support fixed point @samp{move@var{m}} +There may also be a need to support fixed point @samp{mov@var{m}} instructions in and out of floating point registers. Unfortunately, I have forgotten why this was so, and I don't know whether it is still true. If @code{HARD_REGNO_MODE_OK} rejects fixed point values in floating point registers, then the constraints of the fixed point -@samp{move@var{m}} instructions must be designed to avoid ever trying to +@samp{mov@var{m}} instructions must be designed to avoid ever trying to reload into a floating point register. @cindex @code{reload_in} instruction pattern @@ -2400,7 +2400,7 @@ are allocating space from the main stack, do this by emitting a move insn to copy @code{virtual_stack_dynamic_rtx} to operand 0. If you are allocating the space elsewhere, generate code to copy the location of the space to operand 0. In the latter case, you must -ensure this space gets freed when the correspoinding space on the main +ensure this space gets freed when the corresponding space on the main stack is free. Do not define this pattern if all that must be done is the subtraction. |