https://sourceware.org/bugzilla/show_bug.cgi?id=32462
--- Comment #2 from Michael Clark ---
someone on LLVM discourse said on Intel, f3 90 is pause,
independent of REX.B. On AMD, it is pause only if REX.B
is clear. the behavior of rep xchg is unspecified.
so it seems that QEMU code snippet is co
https://sourceware.org/bugzilla/show_bug.cgi?id=32462
--- Comment #1 from Michael Clark ---
QEMU ignores REP prefix and treats REX.B PAUSE as 'xchg eax, r8d':
/* If REX_B is set, then this is xchg eax, r8d, not a nop. */
if (REX_B(s)) {
goto do_xchg_reg_eax;
}
if (prefix
https://sourceware.org/bugzilla/show_bug.cgi?id=32462
Bug ID: 32462
Summary: objdump incorrectly disassembles PAUSE with REX.B
prefix
Product: binutils
Version: 2.42
Status: UNCONFIRMED
Severity: normal
https://sourceware.org/bugzilla/show_bug.cgi?id=32461
--- Comment #4 from Stas Sergeev ---
Why not to stay compatible with
lld here? It seems to be doing the
right thing, at least in my understanding.
So while its definitely up to you,
I really suspect that closing this
ticket is sub-optimal.
--
https://sourceware.org/bugzilla/show_bug.cgi?id=32461
--- Comment #3 from Stas Sergeev ---
OK, thanks.
But what to do?
Use different opts on ld and lld?
lld says using -Ttext-segment is invalid,
and I also suspected the same, because
when I read segments with `readelf -l`,
I see that
Type
https://sourceware.org/bugzilla/show_bug.cgi?id=32461
Andreas Schwab changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=32461
--- Comment #1 from Andreas Schwab ---
[This option is specific to the i386 PE targeted port of the linker]
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=32461
Bug ID: 32461
Summary: ld: unrecognized option '--image-base=0x08148000'
Product: binutils
Version: 2.43.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
C
https://sourceware.org/bugzilla/show_bug.cgi?id=32460
Bug ID: 32460
Summary: section `.note.gnu.property' can't be allocated in
segment 0
Product: binutils
Version: 2.43.1
Status: UNCONFIRMED
Severity: normal
