public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jakub@gcc.gnu.org
To: jakub@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: optimization/5854
Date: Fri, 22 Mar 2002 13:56:00 -0000	[thread overview]
Message-ID: <20020322215605.17811.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/5854; it has been noted by GNATS.

From: jakub@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: optimization/5854
Date: 22 Mar 2002 21:54:46 -0000

 CVSROOT:	/cvs/gcc
 Module name:	egcs
 Branch: 	gcc-3_1-branch
 Changes by:	jakub@gcc.gnu.org	2002-03-22 13:54:45
 
 Modified files:
 	gcc            : ChangeLog 
 	gcc/config/m68hc11: m68hc11.md m68hc11.h m68hc11.c 
 
 Log message:
 	PR optimization/5854
 	* config/m68hc11/m68hc11.h (CONST_OK_FOR_LETTER_VALUE_P): Use K for 0.
 	Shut up warnings.
 	(CONST_DOUBLE_OK_FOR_LETTER_P): Use G for 0.0.
 	(EXTRA_CONSTRAINT): Use S for non-push memory operand.
 	* config/m68hc11/m68hc11.c (m68hc11_split_move): Handle setting from
 	const0 if scratch register was not allocated.
 	(m68hc11_reload_operands, m68hc11_gen_lowpart, m68hc11_gen_highpart,
 	m68hc11_z_replacement): Replace gen_rtx (CONST_INT, VOIDmode, ...)
 	with GEN_INT (...).
 	(m68hc11_reorg): Compute BLOCK_FOR_INSN before reload_cse_regs.
 	* config/m68hc11/m68hc11.md: Replace gen_rtx (CONST_INT, VOIDmode, ...)
 	with GEN_INT (...) everywhere.  Remove constraints in define_split
 	patterns.
 	(movdi_internal, movdf_internal, movsi_internal, movsf_internal): Don't
 	require scratch register for setting 0 into regs/non-pushable memory.
 
 Patches:
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/egcs/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.13152.2.176&r2=1.13152.2.177
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/egcs/gcc/config/m68hc11/m68hc11.md.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.23.8.6&r2=1.23.8.7
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/egcs/gcc/config/m68hc11/m68hc11.h.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.31.2.4&r2=1.31.2.5
 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/egcs/gcc/config/m68hc11/m68hc11.c.diff?cvsroot=gcc&only_with_tag=gcc-3_1-branch&r1=1.32.8.5&r2=1.32.8.6
 


             reply	other threads:[~2002-03-22 21:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 13:56 jakub [this message]
2002-03-22 14:26 optimization/5854 jakub

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020322215605.17811.qmail@sources.redhat.com \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).