public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Kugan <kugan.vivekanandarajah@linaro.org>
Cc: Jeff Law <law@redhat.com>,
	 Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
	 "gcc-patches\@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] Allow REG_EQUAL for ZERO_EXTRACT
Date: Thu, 30 Jul 2015 15:09:00 -0000	[thread overview]
Message-ID: <mvm7fph4rey.fsf@hawking.suse.de> (raw)
In-Reply-To: <55B76ED9.8050108@linaro.org> (Kugan's message of "Tue, 28 Jul	2015 22:00:25 +1000")

Kugan <kugan.vivekanandarajah@linaro.org> writes:

> 	* cse.c (cse_insn): Restoring old behaviour for src_eqv
> 	 when dest and value in the REG_EQUAL are same and dest
> 	 is STRICT_LOW_PART.

This fixes the regression and doesn't introduce any new one.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2015-07-30 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28 11:29 [PATCH 0/2] Set REG_EQUAL when emitting arm_emit_movpair Kugan
2015-06-28 11:30 ` [PATCH 1/2] Allow REG_EQUAL for ZERO_EXTRACT Kugan
2015-06-29 12:07   ` Maxim Kuvyrkov
2015-06-30  4:19     ` Kugan
2015-06-30  7:18       ` Maxim Kuvyrkov
2015-07-05 23:17         ` Kugan
2015-07-06 21:12           ` Jeff Law
2015-07-20  7:15             ` Kugan
2015-07-23 19:57               ` Jeff Law
2015-07-26 20:02               ` Andreas Schwab
2015-07-27  3:10                 ` Kugan
2015-07-28 12:19                 ` Kugan
2015-07-30 15:09                   ` Andreas Schwab [this message]
2015-08-03 19:15                   ` Jeff Law
2015-06-28 11:45 ` [PATCH 2/2] Set REG_EQUAL Kugan
2015-06-29 12:17   ` Maxim Kuvyrkov
2015-07-17  8:12   ` Kugan
2015-07-17  8:37   ` Kyrill Tkachov

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=mvm7fph4rey.fsf@hawking.suse.de \
    --to=schwab@linux-m68k.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kugan.vivekanandarajah@linaro.org \
    --cc=law@redhat.com \
    --cc=maxim.kuvyrkov@linaro.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).