I think I found a solution for my use case. Just look to the code below.
00054160 F6F5E682 MOV 0x000082E6,R5
00054164 F2F88087 MOV R8,0x00008780
00054168 F6F8E882 MOV 0x000082E8,R8
0005416C 8A380170 JB CC24.7,0x00054172
00054170 0D03 JMPR CC_UC,0x00054178
00054172 E6F1FE0A MOV R1,#0x0AFE
00054176 0D02 JMPR CC_UC,0x0005417C
00054178 E6F17E0A MOV R1,#0x0A7E
0005417C F2F5E882 MOV R5,0x000082E8
00054180 F2F43C87 MOV R4,0x0000873C
00054184 E087 MOV R7,#8
00054186 DA078059 CALLS 0x07'0x5980
00022DE6 F6F54E87 MOV 0x0000874E,R5
00022DEA E6F18000 MOV R1,#0x0080
00022DEE C2F415F7 MOVBZ RL2,0x0000F715
00022DF2 C2F53C87 MOVBZ RL2,0x0000873C
00022DF6 DA07A658 CALLS 0x07'0x58A6
First block is the area processing a map. Second block is processing an axis used by the map. Map address is 0x0A7E and axis address is 0x0080. We see that the address 0x0000873C is used in both code sections.
So in order to identitfy my axis address I need first to lookup the table section, get the shared address (0x0000873C) and then process a lookup to the axis section using the shared address. I think this was discussed earlier to this discussion.
Looks very exciting and quite easy to implement.
Well I did it :
E6 F1 XX XX 0D 02 E6 F1 XX XX F2 F5 XX XX F2 F4 MMXX XX E0 87 DA XX XX XX F7 FA XX XX 8A XX XX XX 8A XX XX XX 8A|F6 F5 XX XX E6 F1 MMXX XX C2 F4 XX XX C2 F5 $$0 DA
This expression is just doing a lookup to the 0x0080 address of the above example. You can pipe as many expressions as you need. Each match can be reused in the following expressions using the $$n notation. For instance $$0 is inserting the address returned by the first expression evaluation result. I think this can support complex scenario. You can use several $$ notations in a single expression. Feedbacks are welcome. Github updated so you can test now with your own definitions.