public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Jeff Law <law@redhat.com>
Cc: "gcc-patches@gcc.gnu.org >> gcc-patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][PR target/15184] Fix for direct byte access on x86
Date: Thu, 29 Jan 2015 20:50:00 -0000	[thread overview]
Message-ID: <20150129201331.GD28561@gate.crashing.org> (raw)
In-Reply-To: <54CA4407.5050905@redhat.com>

On Thu, Jan 29, 2015 at 07:30:31AM -0700, Jeff Law wrote:
> @@ -2643,6 +2644,34 @@ try_combine (rtx_insn *i3, rtx_insn *i2, rtx_insn *i1, rtx_insn *i0,
>  		   || GET_CODE (src) == LSHIFTRT)
>  	    nshift++;
>  	}
> +
> +      /* If I0 loads a memory and I3 sets the same memory, then I2 and I3
> +	 are likely manipulating its value.  Ideally we'll be able to combine
> +	 all four insns into a bitfield insertion of some kind. 

"I1 and I2"?

Very simple patch, nice :-)


Segher

  reply	other threads:[~2015-01-29 20:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 15:21 Jeff Law
2015-01-29 20:50 ` Segher Boessenkool [this message]
2015-01-30  8:57   ` Jeff Law
2015-01-29 15:51 Uros Bizjak
2015-01-29 16:06 ` Jakub Jelinek
2015-01-29 16:08   ` Uros Bizjak
2015-01-29 16:23     ` Jakub Jelinek
2015-01-29 21:42       ` H.J. Lu
2015-01-30  9:21 ` Jeff Law
2015-01-30 11:02   ` Uros Bizjak
2015-01-30 11:21     ` Jakub Jelinek
2015-01-30 11:21       ` Uros Bizjak
2015-01-30 11:46         ` Jakub Jelinek
2015-01-30 20:36           ` Jeff Law
2015-01-30 20:37     ` Jeff Law
2015-01-30 11:01 Dominique Dhumieres

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=20150129201331.GD28561@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --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).