Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Terje Mathisen Newsgroups: comp.arch Subject: Re: Concertlina II: Full Circle Date: Wed, 19 Jun 2024 13:26:30 +0200 Organization: A noiseless patient Spider Lines: 46 Message-ID: References: <132536f47d1b160ad3ad0340fc479c1d@www.novabbs.org> <50c85586e1aec0eef53e83cef7cb1d5d@www.novabbs.org> <4mb37jdb25571s1q1pjlc3ludaaks7tukr@4ax.com> <1401408dead0bbc0b1e2ea7e053c873a@www.novabbs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 19 Jun 2024 13:26:31 +0200 (CEST) Injection-Info: dont-email.me; posting-host="5189a7bbc9e672641bc19262bf69249d"; logging-data="2057590"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19rahIYgveFC/6jzD4pAMlBx3fORhtz41w+MuMaQ5hQpQ==" User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.18.2 Cancel-Lock: sha1:4umhcJkC+by+bcaNAgmByGngjrw= In-Reply-To: Bytes: 3530 MitchAlsup1 wrote: > John Savard wrote: > >> On Tue, 18 Jun 2024 21:23:57 +0000, mitchalsup@aol.com (MitchAlsup1) >> wrote: >>> John Savard wrote: > >>>> (1 bit) This indicates whether we're talking about the integer >>>> registers or the floating-point ones. >>> >>> Loops controlled by floating point indexes do not vectorize, however >>> the body of the loop can be any mix of int, logical, memory, or FP >>> instructions. > >> Oh no, my index is always an integer. This bit applies to the >> "live-in" bits - if the loop performs floating-point computation, it's >> floating-point registers that I want to mark as forwarding nodes. > > See, I do not have this distinction, there is but one file. > >> And so you indicate this explicitly in VVM as well. I tended to assume >> only a limited number of registers would be needed to live in, plus I >> have both floating and integer register files, hence the differences. > > It ends up that the majority of register uses in a loop do not need to > be visible outside of the loop. This is almost the contrapositive of > annotating which registers are temporary in the loop. 90%+ of loops do > not even need the index register to be live outside of the loop. This is partly due to programming languages that applies lifetimes to variables, so that an index register which is defined in the scaffolding of the loop (i.e. for (i = 0; i < limit; i++) {}) is invisible as soon as the loop terminates. Without such a restriction, there are many times when it would be very natural to inspect the index in order to determine if this was a normal (counting) exit, or an early exit due to some internal test. Personally, I have still not settled on my preferred way to handle cases like this, but I possibly will do so after I retire. Terje -- - "almost all programming can be viewed as an exercise in caching"