jrmuizel has quit [Remote host closed the connection]
jrmuizel has joined #lima
_whitelogger has joined #lima
dddddd has joined #lima
mardinauskas has joined #lima
ninolein has joined #lima
<mardinauskas>
Multiple solutions, all that matters is when you go out of order, previous instructions did not schedule due to deps. you go right to the wfid 5. issue it, then fetch counter is at 1, column change however is done when the mentioned values equal in the queues. So you gotta skip some instructions to do branch emulation in queues, and skipping is done via indirection.
jrmuizel has quit [Remote host closed the connection]
<mardinauskas>
as far as the chip is concerned, it will increment fetch counter if something was issued then the perfect way is to use back to back loads the same address, and indirection toggler
<mardinauskas>
all the thing is, that there is an enourmous amount of variations how one wants to solve it, to be able to read a single solution you need to know rules, and hence i put lot of theory into code
jrmuizel has quit [Remote host closed the connection]
jrmuizel has joined #lima
jrmuizel has quit [Ping timeout: 272 seconds]
jrmuizel has joined #lima
jrmuizel has quit [Ping timeout: 245 seconds]
jrmuizel has joined #lima
jrmuizel has quit [Ping timeout: 272 seconds]
mardinauskas has joined #lima
<mardinauskas>
it is *pretty* good how the hardware logic is laid out, you should not ask for any better. And this is the both for CPUs and GPUs. And it is not difficult today to make a competing arch either.
jrmuizel has joined #lima
jrmuizel has quit [Ping timeout: 245 seconds]
jrmuizel has joined #lima
jrmuizel has quit [Ping timeout: 244 seconds]
mardinauskas has quit [Quit: Leaving]
drod has joined #lima
Wizzup has quit [Remote host closed the connection]