[Bug gas/24546] x86-64 far jump/call encoding issues

2020-02-12 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 H.J. Lu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug gas/24546] x86-64 far jump/call encoding issues

2020-02-12 Thread jbeulich at suse dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 --- Comment #10 from Jan Beulich --- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=5990e377e5a339bce715fabfc3e45b24b459a7af I don't see a mechanism in the web interface though how to change a bug's status, so I'm

[Bug gas/24546] x86-64 far jump/call encoding issues

2020-01-09 Thread jbeulich at suse dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 --- Comment #9 from Jan Beulich --- The proposed added (AT mode) behavior is to allow lcall and ljmp to also have q suffixes in 64-bit Intel mode, paralleling how other insns (including branching ones) work. Similarly the assembler would then

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-16 Thread jbeulich at novell dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 --- Comment #8 from Jan Beulich --- (In reply to H.J. Lu from comment #7) > Care to make a patch? Well, I've added it to my list of things to look into, but there are various other things higher up that list, so it's not clear at all when

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-15 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 H.J. Lu changed: What|Removed |Added Status|WAITING |NEW --- Comment #5 from H.J. Lu --- (In

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-15 Thread andrew.cooper3 at citrix dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 --- Comment #4 from Andrew Cooper --- (In reply to H.J. Lu from comment #3) > AMD64 manual says: > > CALL FAR pntr16:16 9A cd Far call direct, with the target specified by a far > pointer > contained in the instruction. (Invalid in 64-bit

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-14 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 --- Comment #3 from H.J. Lu --- (In reply to Andrew Cooper from comment #2) > Yes. That works on all 64bit capable processors. > > The encoding which isn't supported in 64bit mode is the ptr:16:{16,32,64} > encoding, which stores the

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-14 Thread andrew.cooper3 at citrix dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 --- Comment #2 from Andrew Cooper --- Yes. That works on all 64bit capable processors. The encoding which isn't supported in 64bit mode is the ptr:16:{16,32,64} encoding, which stores the segment and offset as immediate data operands in the

[Bug gas/24546] x86-64 far jump/call encoding issues

2019-05-14 Thread hjl.tools at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=24546 H.J. Lu changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|