RE: Delay scheduling due to possible future multiple issue in VLIW

2013-07-16 Thread Paulo Matos
ion I have. Regards, Paulo Matos > -Original Message- > From: Maxim Kuvyrkov [mailto:ma...@kugelworks.com] > Sent: 16 July 2013 05:02 > To: Paulo Matos > Cc: gcc@gcc.gnu.org > Subject: Re: Delay scheduling due to possible future multiple issue in VLIW > > Pa

Re: Delay scheduling due to possible future multiple issue in VLIW

2013-07-15 Thread Maxim Kuvyrkov
Paulo, GCC schedule is not particularly designed for VLIW architectures, but it handles them reasonably well. For the example of your code both schedules take same time to execute: 38: 0: r1 = e[r0] 40: 4: [r0] = r1 41: 5: r0 = r0+4 43: 5: p0 = r1!=0 44: 6: jump p0 and 38: 0: r1 = e[r0] 41:

RE: Delay scheduling due to possible future multiple issue in VLIW

2013-06-27 Thread Paulo Matos
Let me add to my own post saying that it seems that the problem is that the list scheduler is greedy in the sense that it will take an instruction from the ready list no matter what when waiting and trying to pair it with later on with another instruction might be more beneficial. In a sense it