<gruetzkopf> i still need a location to run the onyx2 contiuosly
<gruetzkopf> and hand out shells on irix6.5.30 (with licensed compiler suite)
<TD-Linux> >.sv
<TD-Linux> this kills the yosys
<TD-Linux> sorear, I don't think the R4000 is dual issue?
<TD-Linux> I guess if you count integer+float it is
<sorear> no, it's not, I misremembered the order
<TD-Linux> looks like swerv actually has 4 pipes
<TD-Linux> 2 integer, 1 load/store, 1 mult
<TD-Linux> but oly the integer pipes can write back so that's why they only call it dual issue
<sorear> I'd interpret "dual issue" as "two instructions can start in any cycle"
futarisIRCcloud has joined ##openfpga
Stary has quit [Ping timeout: 252 seconds]
GenTooMan has quit [Quit: Leaving]
unixb0y has quit [Ping timeout: 246 seconds]
unixb0y has joined ##openfpga
dj_pi has joined ##openfpga
gsi__ has joined ##openfpga
gsi_ has quit [Ping timeout: 268 seconds]
dj_pi has quit [Ping timeout: 246 seconds]
Flea86 has joined ##openfpga
<cr1901_modern> sorear: What do you mean by "misremembered the order"?
<cr1901_modern> And why doesn't superscalar imply dual issue?
<sorear> cr1901_modern: TD-Linux last comment was about dual issue versus quad issue, both are superscalar
<cr1901_modern> oh oops
mumptai_ has joined ##openfpga
jevinski_ has joined ##openfpga
mumptai has quit [Ping timeout: 240 seconds]
jevinskie has quit [Ping timeout: 268 seconds]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
pie__ has joined ##openfpga
pie_ has quit [Ping timeout: 246 seconds]
<azonenberg> yeah dual issue is a subset of superscalar
<azonenberg> i guess technically you could have a dual issue VLIW
<azonenberg> which is not superscalar because the instructions are scheduled at compile time vs run time
<sorear> I don't normally hear the word "issue" in that context, but my sample size of dsps is lacking
<azonenberg> yeah i just mean, a 2-lane-wide VLIW is clearly dual issue, it executes two instructions per clock
<azonenberg> But it's not superscalar because there's no hazard checking etc
<Bob_Dole> I started reading up, from this discussion mentioning VLIW, and at first thought the R4000 would be in reference to Radeon (HD) 4000.. and then read up to see, no, the MIPS R4000, and not RV770.
Bike has quit [Quit: leaving]
_whitelogger has joined ##openfpga
Miyu has quit [Ping timeout: 245 seconds]
gsi__ is now known as gsi_
ayjay_t has quit [Read error: Connection reset by peer]
ayjay_t has joined ##openfpga
rohitksingh has joined ##openfpga
Asu has joined ##openfpga
rohitksingh has quit [Ping timeout: 244 seconds]
rohitksingh has joined ##openfpga
_whitelogger has joined ##openfpga
rohitksingh has quit [Ping timeout: 240 seconds]
rohitksingh has joined ##openfpga
rohitksingh has quit [Ping timeout: 240 seconds]
Flea86 has quit [Quit: Goodbye and thanks for all the dirty sand ;-)]
dj_pi has joined ##openfpga
Bike has joined ##openfpga
OmniMancer has quit [Quit: Leaving.]
Miyu has joined ##openfpga
dj_pi has quit [Ping timeout: 272 seconds]
lutsabound has joined ##openfpga
Stary has joined ##openfpga
rohitksingh has joined ##openfpga
emeb has joined ##openfpga
Zorix has quit [Ping timeout: 250 seconds]
Zorix has joined ##openfpga
m4ssi has joined ##openfpga
ayjay_t has quit [Read error: Connection reset by peer]
ayjay_t has joined ##openfpga
finsternis has quit [Excess Flood]
finsternis has joined ##openfpga
mumptai_ has quit [Quit: Verlassend]
mumptai has joined ##openfpga
rohitksingh has quit [Ping timeout: 244 seconds]
dj_pi has joined ##openfpga
dj_pi has quit [Ping timeout: 250 seconds]
scrts has joined ##openfpga
scrts has quit [Client Quit]
scrts has joined ##openfpga
m4ssi has quit [Remote host closed the connection]
zem has quit [Ping timeout: 240 seconds]
zem has joined ##openfpga
X-Scale has joined ##openfpga
cr1901_modern1 has joined ##openfpga
cr1901_modern has quit [Ping timeout: 240 seconds]
Flea86 has joined ##openfpga
Asu has quit [Remote host closed the connection]