From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] x86-64: correct segment override prefix generation
Date: Mon, 30 Jul 2012 17:04:00 -0000 [thread overview]
Message-ID: <CAMe9rOr2HedB_bmSAX+ji23N2tBzYDPaV12XFWJxF=TaekPiwA@mail.gmail.com> (raw)
In-Reply-To: <500EDB2202000078000903AF@nat28.tlf.novell.com>
On Tue, Jul 24, 2012 at 8:28 AM, Jan Beulich <JBeulich@suse.com> wrote:
> Despite them being ignored by the CPU, gas issues segment override
> prefixes for other than FS/GS in 64-bit mode. If doing so at all, it
> should clearly do this correctly. Determining the default segment,
> however, requires to take into consideration RegRex (so far, RSP, RBP,
> R12, and R13 were all treated equally here).
>
> 2012-07-24 Jan Beulich <jbeulich@suse.com>
>
> * config/tc-i386-intel.c (build_modrm_byte): Split determining
> default segment from figuring out encoding. Honor RegRex for
> the former.
>
> --- a/gas/config/tc-i386.c
> +++ b/gas/config/tc-i386.c
> @@ -5733,18 +5733,14 @@ build_modrm_byte (void)
> i.sib.base = i.base_reg->reg_num;
> /* x86-64 ignores REX prefix bit here to avoid decoder
> complications. */
> - if ((i.base_reg->reg_num & 7) == EBP_REG_NUM)
> - {
> + if (!(i.base_reg->reg_flags & RegRex)
> + && (i.base_reg->reg_num == EBP_REG_NUM
> + || i.base_reg->reg_num == ESP_REG_NUM))
> default_seg = &ss;
> - if (i.disp_operands == 0)
> - {
> - fake_zero_displacement = 1;
> - i.types[op].bitfield.disp8 = 1;
> - }
> - }
> - else if (i.base_reg->reg_num == ESP_REG_NUM)
> + if (i.base_reg->reg_num == 5 && i.disp_operands == 0)
> {
> - default_seg = &ss;
> + fake_zero_displacement = 1;
> + i.types[op].bitfield.disp8 = 1;
> }
> i.sib.scale = i.log2_scale_factor;
> if (i.index_reg == 0)
>
Please provide a testcase to show the correct behavior.
Thanks.
--
H.J.
next prev parent reply other threads:[~2012-07-30 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 15:28 Jan Beulich
2012-07-30 17:04 ` H.J. Lu [this message]
2012-08-07 10:42 ` [PATCH, v2] " Jan Beulich
2012-08-07 13:46 ` H.J. Lu
2012-08-07 13:56 ` Jan Beulich
2012-08-07 14:03 ` 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='CAMe9rOr2HedB_bmSAX+ji23N2tBzYDPaV12XFWJxF=TaekPiwA@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).