summaryrefslogtreecommitdiff
path: root/gcc/config/frv/frv.md
diff options
context:
space:
mode:
authorkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2005-04-01 03:42:55 +0000
committerkazu <kazu@138bc75d-0d04-0410-961f-82ee72b054a4>2005-04-01 03:42:55 +0000
commit06b27565fde517f9f8ac1f4fc7fc9828c4cc95c2 (patch)
tree782893b0afb24d21b87a6216e40df5e5f887e02f /gcc/config/frv/frv.md
parentf35e07c2a3efc9ebe906a990e4eee12adc435e0a (diff)
downloadgcc-06b27565fde517f9f8ac1f4fc7fc9828c4cc95c2.tar.gz
* cgraphunit.c, dbxout.c, flow.c, gcse.c, gimplify.c,
lambda-code.c, loop.c, machmode.def, mips-tfile.c, modulo-sched.c, passes.c, postreload-gcse.c, tree-eh.c, tree-ssa-ccp.c, varasm.c, config/frv/frv.c, config/frv/frv.h, config/frv/frv.md, config/i386/i386.c, config/i386/i386.h, config/i386/i386.md, config/rs6000/predicates.md, config/rs6000/rs6000.c, config/s390/fixdfdi.h, config/s390/s390.c, config/stormy16/stormy16.c, config/stormy16/stormy16.md, config/vax/vax.md: Fix comment typos. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@97362 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/config/frv/frv.md')
-rw-r--r--gcc/config/frv/frv.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/config/frv/frv.md b/gcc/config/frv/frv.md
index 4515c0b44dd..a81bc8b940e 100644
--- a/gcc/config/frv/frv.md
+++ b/gcc/config/frv/frv.md
@@ -1206,7 +1206,7 @@
(eq_attr "type" "sqrt_single"))
"(f1|f0) + fr550_float")
-;; Synthetic units for enforcing media issue restructions. Certain types
+;; Synthetic units for enforcing media issue restrictions. Certain types
;; of insn in M2 conflict with certain types in M0:
;;
;; M2
@@ -5913,7 +5913,7 @@
;; Called after register allocation to add any instructions needed for the
;; epilogue. Using an epilogue insn is favored compared to putting all of the
;; instructions in the FUNCTION_EPILOGUE macro, since it allows the scheduler
-;; to intermix instructions with the restires of the caller saved registers.
+;; to intermix instructions with the restores of the caller saved registers.
;; In some cases, it might be necessary to emit a barrier instruction as the
;; first insn to prevent such scheduling.
(define_expand "epilogue"