https://bugs.kde.org/show_bug.cgi?id=417187
--- Comment #16 from Julian Seward <jsew...@acm.org> --- Hi Stefan, Thank you for the analyses, patches and testing. Overall, your solutions look good to me. I have just one question, regarding this patch: Subject: [PATCH 1/2] mips: Treat delay slot as part of previous instruction Do so by recursively calling disInstr_MIPS_WRK() if the instruction currently being disassembled is a branch/jump, effectively combining them into one IR instruction. Is there any danger of this being incorrect even in pathological cases (eg, the branch delay slot itself holding a branch, whose delay slot also holds a branch, etc? -- or something like that?) I mean .. is there any way that this could possibly fail, given the strangest, most artificial code sequence? Or is it always safe? Also I was a bit concerned about the recursive use of disInstr_MIPS_WRK. Closely related to the previous question .. is there any way to cause infinite, or at least arbitrarily deep, recursion? -- You are receiving this mail because: You are watching all bug changes.
