Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Thu, 12 Apr 2012 23:34:44 -0500
Message-ID: <4F87ACE1.4060104@SPAM.comp-arch.net>
Date: Thu, 12 Apr 2012 21:34:41 -0700
From: "Andy (Super) Glew" <andy@SPAM.comp-arch.net>
Reply-To: andy@SPAM.comp-arch.net
Organization: comp-arch.net
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
Newsgroups: comp.arch
Subject: Re: Indirect Bit
References: <4F84FB1E.6CD1FC88@sonic.net> <4F86ECC6.4060405@SPAM.comp-arch.net> <7207568.240.1334250963776.JavaMail.geo-discussion-forums@yncd8> <26200843.276.1334254070673.JavaMail.geo-discussion-forums@vbhy1>
In-Reply-To: <26200843.276.1334254070673.JavaMail.geo-discussion-forums@vbhy1>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 10
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-ZsxTtSdOOHNIQOiKWXKQqrNKC+5JMCysZyiKk+DuzhKEaB3/5j3ZteTi0X3pqpLf3DMrZZ7kzYDEE0j!LMkJgGu6nZqGapTrlXqIU7HXT1aDPw/7VgJhT/GIS1kah4ezw5VS/gaO/fWT
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 1916
Xref: csiph.com comp.arch:6518

On 4/12/2012 11:07 AM, jacko wrote:
> An indirect chase read or write instruction pair, with indirection count, and offset literals (one for each count).
>
> Such as 'load 0(r1), 3(r2), 6, 7, 3' may be very useful. But would be microcoded I suppose. With the 0 count being register direct.

Microcoded if you execute it at the CPU.

If executed outsiede the processor, well, each state transition may be 
executed at a memory node, and then the operation may have to be 
forwarded to the memory node where the next piece of data lives.