End the indirect jump when potential hotspot is detected

[qwe661234]

Currently, the indirect jump does not switch to T1C when potential hotspot is detected, it would make execution stuck in interpreter mode. This modification make execution end when potential hotspot is detected.

[jserv]

The following code snip appears several times in src/emulate.c and src/rv32_template.c, and can you unify by jumping the label in RVOP?

        rv->csr_cycle = cycle;
        rv->PC = PC;
        return true;

[qwe661234]

The following code snip appears several times in src/emulate.c and src/rv32_template.c, and can you unify by jumping the label in RVOP?

        rv->csr_cycle = cycle;
        rv->PC = PC;
        return true;

However, since this label is within the scope of a function, I can replace them with a MACRO.

[jserv]

However, since this label is within the scope of a function, I can replace them with a MACRO.

That sounds good. The label will be named end_op. The term "op" (operation) is preferred over "insn" (instruction) to clearly differentiate between RISC-V instructions and the IR operations derived from them. Our interpreter specifically manipulates these IR operations, rather than the direct RISC-V instructions.

[jserv]

Rephrase "This modification make execution end when potential hotspot is detected" to

This revision ensures the execution halts upon identifying a potential hotspot. It aims to make the execution process more efficient by stopping when a significant area of code usage is detected, allowing for targeted optimization.