Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: John Savard Newsgroups: comp.arch Subject: Re: Concertlina II: Full Circle Date: Mon, 17 Jun 2024 15:57:53 -0600 Organization: A noiseless patient Spider Lines: 26 Message-ID: References: <132536f47d1b160ad3ad0340fc479c1d@www.novabbs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Date: Mon, 17 Jun 2024 23:57:53 +0200 (CEST) Injection-Info: dont-email.me; posting-host="ede4fe1034f2fa34adb65a1cf243f303"; logging-data="1003099"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX186r5jQBiY8zwDsxRMDQNOdJRtvig1Mt2Y=" Cancel-Lock: sha1:JYabnHe/lI4FUJFNCAk7YfWcvAg= X-Newsreader: Forte Free Agent 3.3/32.846 Bytes: 1915 On Mon, 17 Jun 2024 20:20:03 +0000, mitchalsup@aol.com (MitchAlsup1) wrote: >As to looping, I faced the same delimma and came to a different >conclusion:: >You don't do it in 1 instruction, instead, you do it in a way where >your >2 instruction encoding executes one of the instructions only once. I >call >this bookending the loop. I considered something like that. My problem was that encoding the parameters of the loop in one instruction takes too much space. So the first thing I thought of was to put some of them in the instruction that repeats the loop. The proiblem was, though, that since the instruction that repeats the loop points to the start of the loop in memory, it's a memory-reference instruction, so there isn't much extra room left in it. However, there is a little room left, so I may indeed go back and explore that possibility some more. John Savard