H.J. Lu hjl.tools@gmail.com
Thu Sep 13 14:40:00 GMT 2018

• Previous message (by thread): [PATCH] i386: Update VexW field for VEX instructions
• Next message (by thread): Commit: Initialise expression structures in dwarf2dbg.c
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Thu, Sep 13, 2018 at 6:53 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 13.09.18 at 15:25, <hjl.tools@gmail.com> wrote:
>> This is what I checked in.  VexW is needed for -mvexwig=[0|1] I am working
>> on.
>
> And on 3rd look I get the impression that you've committed exactly the
> parts that I think should not have been committed, and left out the
> ones that I think should have gone in (rendering the ChangeLog entry
> and commit message stale, as both still claim "Remove VexW=1 from
> WIG VEX movq and vmovq").

They were lost during merge.  This is what I checked in.

Thanks.

-- 
H.J.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-x86-Remove-VexW-1-from-WIG-VEX-movq-and-vmovq.patch
Type: text/x-patch
Size: 6447 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/binutils/attachments/20180913/e2f2c437/attachment.bin>

---

• Previous message (by thread): [PATCH] i386: Update VexW field for VEX instructions
• Next message (by thread): Commit: Initialise expression structures in dwarf2dbg.c
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list