This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Applied: Corrected ChangeLog entry for ns32k changes of 01-27
- To: gcc-patches at gcc dot gnu dot org
- Subject: Applied: Corrected ChangeLog entry for ns32k changes of 01-27
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- Date: Sat, 29 Jan 2000 11:29:43 -0500 (EST)
Hi.
I corrected the ChangeLog entry for Ian Dall's and mine changes.
It had a leftover part that referred to a fix that was
eventually corrected in genrecog.c rather than ns32k.md and
therefore left out from the bulk patch as discussed with Ian.
I claim obviousness, thus installed this.
Do we need to copy fixes for ChangeLog entries such as this to
gcc-patches, or is it ok to just silently apply them?
Index: ChangeLog
===================================================================
RCS file: /cvs/gcc/egcs/gcc/ChangeLog,v
retrieving revision 1.5564
diff -p -c -r1.5564 ChangeLog
*** ChangeLog 2000/01/29 03:11:20 1.5564
--- ChangeLog 2000/01/29 15:59:49
*************** Fri Jan 28 10:57:58 2000 Jason Eckhardt
*** 178,185 ****
known at compile time.
* ns32k/ns32k.md: Alternate constraints for multiply-add instructions.
(udivmodsi4, udivmodhi4, udivmodqi4): Use nonimmediate_operand
! instead of reg_or_mem_operand. Use VOIDmode for load or push
! effective address.
* ns32k/ns32k.md: Use nonimmediate_operand or stricter for outputs,
not general_operand. Similarly use "=rm" or stricter, not "=g".
--- 178,184 ----
known at compile time.
* ns32k/ns32k.md: Alternate constraints for multiply-add instructions.
(udivmodsi4, udivmodhi4, udivmodqi4): Use nonimmediate_operand
! instead of reg_or_mem_operand.
* ns32k/ns32k.md: Use nonimmediate_operand or stricter for outputs,
not general_operand. Similarly use "=rm" or stricter, not "=g".
brgds, H-P