bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/25012] pushq/popq %gs/%fs in .code64 now unsupported


From: hjl.tools at gmail dot com
Subject: [Bug gas/25012] pushq/popq %gs/%fs in .code64 now unsupported
Date: Fri, 04 Oct 2019 15:08:17 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=25012

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.34

--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for 2.34 by

commit 3f9aad111cea2f25877d0a6b404956769c14faee
Author: Jan Beulich <address@hidden>
Date:   Fri Sep 20 10:18:15 2019 +0200

    x86-64: fix handling of PUSH/POP of segment register

    Commit 21df382b91 ("x86: fold SReg{2,3}") went too far: Folding 64-bit
    PUSH/POP templates into non-64-bit ones isn't correct, due to the
    different operand widths, and hence suffixes permitted. Restore the
    separate templates.

    Add tests of PUSH/POP with q suffix and %fs/%gs operands to the
    testsuite. While doing so also add PUSHF/POPF ones _without_ suffix.

and on 2.33 branch by

commit 20057c8c5e67ffdfb1a7b6a4ef3d337ea27663d1
Author: Jan Beulich <address@hidden>
Date:   Fri Sep 20 10:18:15 2019 +0200

    x86-64: fix handling of PUSH/POP of segment register

    Commit 21df382b91 ("x86: fold SReg{2,3}") went too far: Folding 64-bit
    PUSH/POP templates into non-64-bit ones isn't correct, due to the
    different operand widths, and hence suffixes permitted. Restore the
    separate templates.

    Add tests of PUSH/POP with q suffix and %fs/%gs operands to the
    testsuite. While doing so also add PUSHF/POPF ones _without_ suffix.

    (cherry picked from commit 3f9aad111cea2f25877d0a6b404956769c14faee)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]