This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[patch] h8300.md: Remove an unnecessary '&' constraint.


Hi,

Attached is a patch to remove an unnecessary '&' constraint.

In these insns, there is only one register is involved.  The '&'
constraint simply does not make sense.

I don't see any difference in generated code with or without this '&'
as far as I can tell from libc and libm of newlib.

Tested on h8300 port.  Committed.

Kazu Hirata

2003-11-28  Kazu Hirata  <kazu@cs.umass.edu>

	* config/h8300/h8300.md (*subhi3_h8300): Remove '&' from the
	constraint.
	(*subhi3_h8300hs): Likewise.

Index: h8300.md
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/h8300/h8300.md,v
retrieving revision 1.247
diff -u -r1.247 h8300.md
--- h8300.md	27 Nov 2003 14:47:06 -0000	1.247
+++ h8300.md	27 Nov 2003 17:24:29 -0000
@@ -971,7 +971,7 @@
   "")
 
 (define_insn "*subhi3_h8300"
-  [(set (match_operand:HI 0 "register_operand" "=r,&r")
+  [(set (match_operand:HI 0 "register_operand" "=r,r")
 	(minus:HI (match_operand:HI 1 "general_operand" "0,0")
 		  (match_operand:HI 2 "nonmemory_operand" "r,n")))]
   "TARGET_H8300"
@@ -982,7 +982,7 @@
    (set_attr "cc" "set_zn,clobber")])
 
 (define_insn "*subhi3_h8300hs"
-  [(set (match_operand:HI 0 "register_operand" "=r,&r")
+  [(set (match_operand:HI 0 "register_operand" "=r,r")
 	(minus:HI (match_operand:HI 1 "general_operand" "0,0")
 		  (match_operand:HI 2 "nonmemory_operand" "r,n")))]
   "TARGET_H8300H || TARGET_H8300S"


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]