From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Binutils <binutils@sourceware.org>, Michael Matz <matz@suse.de>
Subject: Re: [committed, PATCH] Remove Disp16|Disp32 from 64-bit direct branches
Date: Mon, 18 May 2015 12:18:00 -0000 [thread overview]
Message-ID: <CAMe9rOrgO4=CHm2RY6vmnc_1xxE-NKpk8BU3GLCdx2AynNtMRQ@mail.gmail.com> (raw)
In-Reply-To: <5559EDB9020000780007B0A3@mail.emea.novell.com>
On Mon, May 18, 2015 at 4:48 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>> perhaps also that CpuAMD64 and CpuIntel64 would imply Cpu64 (as
>>> their names already suggest).
>>
>> They are just a bit. Make them to implement Cpu64 means adding more
>> codes to x86 assembler without any benefit. If you can share with me
>> what you have in mind, I will see what I can do.
>
> Ah, no, I didn't mean the assembler to do more work. Instead I
> thought that the generator utility could set Cpu64 alongside either
> of the new ones, thus keeping the opcode table slightly better
> readable.
Sure. We will do that when we add CPU_AMD64_FLAGS, like:
{ "CPU_AMD64_FLAGS",
"CpuAMD64|Cpu64" },
I haven't found a need for it yet.
--
H.J.
prev parent reply other threads:[~2015-05-18 12:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 21:23 H.J. Lu
2015-05-12 10:41 ` Jan Beulich
2015-05-12 11:54 ` H.J. Lu
2015-05-12 12:20 ` Jan Beulich
2015-05-12 12:37 ` H.J. Lu
2015-05-12 13:03 ` Jan Beulich
2015-05-12 13:37 ` H.J. Lu
2015-05-12 13:49 ` Michael Matz
2015-05-12 13:57 ` H.J. Lu
2015-05-12 14:31 ` Michael Matz
2015-05-12 14:49 ` H.J. Lu
2015-05-12 15:14 ` Michael Matz
2015-05-12 15:21 ` H.J. Lu
2015-05-12 15:32 ` Michael Matz
2015-05-12 14:59 ` Jan Beulich
2015-05-12 15:03 ` H.J. Lu
2015-05-12 15:09 ` Jan Beulich
2015-05-12 15:11 ` H.J. Lu
2015-05-12 15:17 ` Jan Beulich
2015-05-12 15:37 ` Michael Matz
2015-05-12 15:43 ` H.J. Lu
2015-05-12 15:47 ` Michael Matz
2015-05-12 16:00 ` H.J. Lu
2015-05-12 16:03 ` Michael Matz
2015-05-12 16:08 ` H.J. Lu
2015-05-13 6:18 ` Jan Beulich
2015-05-13 11:35 ` H.J. Lu
2015-05-13 12:27 ` Jan Beulich
2015-05-13 13:15 ` H.J. Lu
2015-05-13 12:34 ` Michael Matz
2015-05-13 13:32 ` H.J. Lu
2015-05-13 16:50 ` Maciej W. Rozycki
2015-05-13 16:53 ` H.J. Lu
2015-05-15 6:39 ` Jan Beulich
2015-05-15 16:52 ` H.J. Lu
2015-05-18 7:05 ` Jan Beulich
2015-05-18 11:22 ` H.J. Lu
2015-05-18 11:48 ` Jan Beulich
2015-05-18 12:18 ` 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='CAMe9rOrgO4=CHm2RY6vmnc_1xxE-NKpk8BU3GLCdx2AynNtMRQ@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=macro@linux-mips.org \
--cc=matz@suse.de \
/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).