From: Jan Beulich <jbeulich@suse.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>
Subject: [PATCH v8 0/2] x86: replace adhoc (partly wrong) ambiguous operand checking for MOVSX/MOVZX
Date: Fri, 14 Feb 2020 12:21:00 -0000 [thread overview]
Message-ID: <92fd2cf8-90a0-98f8-9453-c49d911daec6@suse.com> (raw)
1: x86: replace adhoc (partly wrong) ambiguous operand checking for MOVSX/MOVZX
2: x86/AT&T: don't default to byte source for ambiguous for MOVSX/MOVZX
v8 is just to split out the controversial part, in the hope
that at least the main change can go in.
Jan
next reply other threads:[~2020-02-14 12:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 12:21 Jan Beulich [this message]
2020-02-14 12:26 ` [PATCH v8 2/2] x86/AT&T: don't default to byte source for ambiguous " Jan Beulich
2020-02-14 12:28 ` H.J. Lu
2020-02-14 13:13 ` Jan Beulich
2020-02-14 13:54 ` Jan Beulich
2020-02-14 14:16 ` H.J. Lu
2020-02-14 14:23 ` Jan Beulich
2020-02-14 14:26 ` H.J. Lu
2020-02-14 14:32 ` Jan Beulich
2020-02-14 14:38 ` H.J. Lu
2020-02-14 15:47 ` Jan Beulich
2020-02-14 15:52 ` Jan Beulich
2020-02-14 16:26 ` H.J. Lu
2020-02-14 16:36 ` Jan Beulich
2020-02-14 16:52 ` H.J. Lu
2020-02-17 13:44 ` Jan Beulich
2020-02-17 14:14 ` H.J. Lu
2020-02-17 15:37 ` Jan Beulich
2020-02-17 16:56 ` H.J. Lu
2020-02-17 17:04 ` Jan Beulich
2020-02-17 17:19 ` H.J. Lu
2020-02-18 7:44 ` Jan Beulich
2020-02-14 12:26 ` [PATCH v8 1/2] x86: replace adhoc (partly wrong) ambiguous operand checking " Jan Beulich
2020-02-14 12:31 ` H.J. Lu
2020-02-14 12:34 ` H.J. Lu
2020-02-14 12:42 ` Jan Beulich
2020-02-14 12:49 ` H.J. Lu
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=92fd2cf8-90a0-98f8-9453-c49d911daec6@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).