[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 mod

[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] New: x86-64 far jump/call encoding issues

2019-05-11 Thread andrew.cooper3 at citrix dot com
Assignee: unassigned at sourceware dot org Reporter: andrew.cooper3 at citrix dot com Target Milestone: --- I have some problems when trying to encode the 64bit forms of far call/jump. Like all other far operations in 64bit, lcall/ljmp default to a 32bit operand, and require