https://gcc.gnu.org/g:9ab2a37a96749fdf4ff3514c7ed75dad2cd32bfe
commit r17-1125-g9ab2a37a96749fdf4ff3514c7ed75dad2cd32bfe Author: Dhruv Chawla <[email protected]> Date: Wed May 20 12:16:11 2026 +0000 rx: Fix typos in rx.cc and rx.md Signed-off-by: Dhruv Chawla <[email protected]> gcc/ChangeLog: * config/rx/rx.cc (rx_print_operand): Fix typos. (rx_expand_epilogue): Likewise. * config/rx/rx.md: Likewise. Diff: --- gcc/config/rx/rx.cc | 4 ++-- gcc/config/rx/rx.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/config/rx/rx.cc b/gcc/config/rx/rx.cc index 4078580f6ad4..038f93431f43 100644 --- a/gcc/config/rx/rx.cc +++ b/gcc/config/rx/rx.cc @@ -867,7 +867,7 @@ rx_print_operand (FILE * file, rtx op, int letter) rtx base = XEXP (op, 0); rtx index = XEXP (op, 1); - /* Check for a swaped index register and scaling factor. + /* Check for a swapped index register and scaling factor. Not sure if this can happen, but be prepared to handle it. */ if (CONST_INT_P (base) && REG_P (index)) { @@ -2081,7 +2081,7 @@ rx_expand_epilogue (bool is_sibcall) unsigned int reg; unsigned HOST_WIDE_INT total_size; - /* FIXME: We do not support indirect sibcalls at the moment becaause we + /* FIXME: We do not support indirect sibcalls at the moment because we cannot guarantee that the register holding the function address is a call-used register. If it is a call-saved register then the stack pop instructions generated in the epilogue will corrupt the address diff --git a/gcc/config/rx/rx.md b/gcc/config/rx/rx.md index b3398ab9fc53..1bd80fd3e2e5 100644 --- a/gcc/config/rx/rx.md +++ b/gcc/config/rx/rx.md @@ -2064,7 +2064,7 @@ ;; combiner bridge patterns. Especially when the memory operands have a ;; displacement, the resulting patterns look too complex. ;; Instead we manually look around the matched insn to see if there is a -;; preceeding memory load and a following memory store of the modified register +;; preceding memory load and a following memory store of the modified register ;; which can be fused into the single *_in_memory insn. ;; Do that before register allocation, as it can eliminate one temporary ;; register that needs to be allocated.
