On 16 November 2012 03:36, John Dravnieks <[email protected]> wrote: > * or for an execute > EX R15,Execute_target > static loctr > Execute_target clc operand1(0),operand2 > code loctr > > One big advantage of this technique is that the USING environment for the > target is the same as the EXecute instruction.
Yes, it's vital that the same USING environment applies, or things get very ugly to read. I don't trust the remarks on EX anymore to tell me what the target does (and remark should tell me the purpose of the instruction, not it's working...) I like your idea to open up an area with LOCTR, assuming you can reach it there. My INLINEX macro generates a branch over the target when I can't afford to invoke it again (like with XC). Maybe smarter people can make the trade-off between an unconditional relative branch and having the target in the same cache line. Fortunately with HLASM such a change would only be in my macro, not in dozens of places in the source... Rob
