public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bschmidt@redhat.com>
To: Jeff Law <law@redhat.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA] [PATCH] Fix invalid redundant extension elimination for rl78 port
Date: Mon, 23 Nov 2015 23:43:00 -0000	[thread overview]
Message-ID: <5653A3AE.9040302@redhat.com> (raw)
In-Reply-To: <56537379.4030101@redhat.com>

> As I mentioned in a prior message on the subject, this is only a problem
> when the source/dest of the extension are the same.  When the
> source/dest of the extension are different, we only optimize when the
> original set and extension are in the same block and we verify that all
> affected registers are not set/used between the original set and the
> extension.
> Bootstrapped and regression tested on x86_64-linux-gnu.  Also tested
> execute.exp on rl78 with no regressions.

Ok.


Bernd

  reply	other threads:[~2015-11-23 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 20:16 Jeff Law
2015-11-23 23:43 ` Bernd Schmidt [this message]
2015-12-01 19:32 ` Richard Sandiford
2015-12-16 19:09   ` Jeff Law
2015-12-16 20:35   ` Jeff Law

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=5653A3AE.9040302@redhat.com \
    --to=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    /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).