Loading an adcon.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [[email protected]] on behalf of Tony Harminc [[email protected]] Sent: Monday, May 3, 2021 1:16 PM To: [email protected] Subject: Re: Ensuring LRL 2nd operand alignment On a more general topic, why does LRL exist in the first place? Why would any programmer (or compiler) use LRL in preference to IILF or one of the other immediate instructions? (And why is there LGFI but no LFI?) Surely immediate instructions are generally faster than relative ones. Some of them are longer, but not in this case. Yes, of course the storage operand of LRL can change in a way that the immediate operand of IILF is unlikely to. But still, without extreme Binder tricks, I can't think that an operand that's at a fixed relative distance from the instruction is likely to be able to be placed in dynamic storage while the instruction isn't. Does someone have a use case for LRL? Tony H.
