Skip to content

ori instructions mistakenly shown as nop #218

Open
@Cuyler36

Description

@Cuyler36

When disassembling, objdiff will show ori r0, r0, imm as nop <imm> if there are relocations in play. Since the immediate is 0 at disassembly, it is technically a nop instruction. The issue can be traced back to ppc750cl here.

ori r0, r0, ksNesMainLoop2@l // this gets interpreted as a nop

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions