Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Malcolm Beattie Newsgroups: comp.arch Subject: Re: Arm ldaxr / stxr loop question Date: Mon, 11 Nov 2024 18:17:54 -0000 (UTC) Organization: A noiseless patient Spider Lines: 27 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 11 Nov 2024 19:17:54 +0100 (CET) Injection-Info: dont-email.me; posting-host="e3bd5248caf55c452512b0cd3baac3a1"; logging-data="1174029"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18lsiK6GUp+kcetiwEcc9CtpRGmti9fdGc=" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:16fl+4cI0fiDssstCP7w3aAO+2c= Bytes: 2093 On 2024-11-10, Lawrence D'Oliveiro wrote: > On Sun, 10 Nov 2024 01:26:22 +0000, MitchAlsup1 wrote: > >> It reads better without explanation ... > > Reminds me of the “EIEIO” instruction from IBM POWER (or was it only > PowerPC). > > Can anybody find any other example of any IBM engineer ever having a sense > of humour? Ever? One of the resource types in JES2, the batch subsystem for z/OS, is BERT ("Block Extension Reuse Table") and needs some sizing/tuning by the sysprog. Not too noticeable as humourous but for low-level use from Assembler some of the macros which manipulate them allow you to (1) copy one into memory, i.e. "Deliver Or Get" a BERT (2) define a hook to get control when a BERT is released, i.e "Do It Later" for a BERT release. (3) generate a control block for a related data area, i.e. a "Collector Attribute Table" for BERTs. These macros are (1) $DOGBERT (2) $DILBERT (3) $CATBERT --Malcolm