public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] x86: Properly encode vmovd with 64-bit memeory
Date: Mon, 08 Jan 2018 13:08:00 -0000	[thread overview]
Message-ID: <CAMe9rOr4cJtS6PeqkHrr=LyGiPoeOzTtjLz===x_fgmsBF0T7w@mail.gmail.com> (raw)
In-Reply-To: <5A53788A020000780019C359@prv-mh.provo.novell.com>

On Mon, Jan 8, 2018 at 4:56 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 08.01.18 at 13:34, <hjl.tools@gmail.com> wrote:
>> This is what I am checking in.
>
> Thanks, yet I still have a point to make: the AVX vmovd templates
> don't participate in SSE2AVX handling, hence continuing to allow
> 64-bit memory operands there doesn't look necessary. The SSE2AVX
> pattern is a movd one.

Only allow 64-bit register operand with vmovd is kind of tricky.  You can
give it a try.


-- 
H.J.

      reply	other threads:[~2018-01-08 13:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  1:18 H.J. Lu
2018-01-08  8:48 ` Jan Beulich
2018-01-08 11:14   ` H.J. Lu
2018-01-08 11:22     ` H.J. Lu
2018-01-08 11:36       ` Jan Beulich
2018-01-08 11:49         ` H.J. Lu
2018-01-08 11:54           ` Jan Beulich
2018-01-08 11:57             ` H.J. Lu
2018-01-08 12:08               ` Jan Beulich
2018-01-08 11:39     ` Jan Beulich
2018-01-08 11:52       ` H.J. Lu
2018-01-08 12:13         ` Jan Beulich
2018-01-08 12:17           ` H.J. Lu
2018-01-08 12:34             ` H.J. Lu
2018-01-08 12:56               ` Jan Beulich
2018-01-08 13:08                 ` H.J. Lu [this message]

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='CAMe9rOr4cJtS6PeqkHrr=LyGiPoeOzTtjLz===x_fgmsBF0T7w@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=binutils@sourceware.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).