My intention was to make things consistent for readability. In the case of gen_jz_ecx_string(), jmp_next[1] is already the "not taken" case. However, looks like the meaning of jmp_next changes in the case of a TB loop, it does not point to the next TB to execute any more. Anyway, I thought this patch can reduce some confusion.
On Sun, Jun 23, 2013 at 2:22 PM, Richard Henderson <r...@twiddle.net> wrote: > On 06/22/2013 09:10 AM, Zhihui Zhang wrote: > > This way, jmp_next[0] means "taken" for both conditional jumps AND > unconditional jumps. > > Currently, it has opposite meanings for the two cases. > > So? There's no proscribed meaning for the 0 and 1 indices. > > > r~ >
