'Just as the sun’s rays radiate outward, so too does the Tiffany Soleste® engagement ring. 
Tips and tricks First of all, read the page. It explains how to deal with most decompilation problems.
Below is a mix of other useful information that did not fit into any other page: • • • • • • • • Sometimes the decompiler can be overly aggressive and optimize references to volatile memory completely away. A typical situation like the following: device_ready DCD?; VOLATILE! MOV R0, =device_ready LDR R1, [R0] LOOP: LDR R2, [R0] SUB R2, R1 BEQ LOOP can be decompiled into while ( 1 ); because the decompiler assumes that a variable can not change its value by itself and it can prove that r0 continues to point to the same location during the loop.
To prevent such optimization, we need to mark the variable as volatile. Currently the decompiler considers memory to be volatile if it belongs to a segment with one of the following names: IO, IOPORTS, PORTS, VOLATILE. The character case is not important. Sometimes the decompiler does not optimize the code enough because it assumes that variables may change their values.
For example, the following code: LDR R1, =off_45934 MOV R2, #0 ADD R3, SP, #0x14+var_C LDR R1, [R1] LDR R1, [R1]; int BL _IOServiceOpen can be decompiled into IOServiceOpen(r0_1, *off_45934, 0) but this code is much better: IOServiceOpen(r0_1, mach_task_self, 0) because off_45934 DCD _mach_task_self is a pointer that resides in constant memory and will never change its value.