[Nasm-bugs] [Bug 3392488] New: mach-o dead striping fix breaks x86 assembly

noreply-nasm at gorcunov.org noreply-nasm at gorcunov.org
Tue May 29 09:48:42 PDT 2018


https://bugzilla.nasm.us/show_bug.cgi?id=3392488

            Bug ID: 3392488
           Summary: mach-o dead striping fix breaks x86 assembly
           Product: NASM
           Version: 2.14 (development)
          Hardware: Macintosh
                OS: Mac OS
            Status: OPEN
          Severity: critical
          Priority: Medium
         Component: Assembler
          Assignee: nobody at nasm.us
          Reporter: afish at apple.com
                CC: gorcunov at gmail.com, hpa at zytor.com, nasm-bugs at nasm.us
     Obtained from: Binary from nasm.us

Created attachment 411645
  --> https://bugzilla.nasm.us/attachment.cgi?id=411645&action=edit
Failing example

This is related to 3392469

It looks like the object relocations are trigging the check for no relocations
in the macho64 text section. Hopefully this is just a bug conflating the object
and executable relocation in the check, and skipping the object relocations
would fix the issue?

nasm_fix -f macho64 -o IoFifoSev.o  IoFifoSev.nasm
IoFifoSev.nasm:37: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:43: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:51: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:62: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:90: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:94: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:97: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:103: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:126: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:130: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:133: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:139: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:162: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:166: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:169: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:175: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:198: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:202: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:205: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:211: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:234: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:238: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:241: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:247: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:270: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:274: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:277: error: Unsupported non-32-bit Macho-O relocation [2]
IoFifoSev.nasm:283: error: Unsupported non-32-bit Macho-O relocation [2]

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


More information about the Nasm-bugs mailing list