Instruction pipe line delay?

ayewinoung@googlemail.com
Fri, 28 Nov 2008 15:01:01 -0800 (PST)

          From comp.compilers

Related articles
Instruction pipe line delay? ayewinoung@googlemail.com (2008-11-28)
Re: Instruction pipe line delay? llib-xoc@sbcglobal.net (Bill Cox) (2008-11-29)
| List of all articles for this month |

From: ayewinoung@googlemail.com
Newsgroups: comp.compilers
Date: Fri, 28 Nov 2008 15:01:01 -0800 (PST)
Organization: Compilers Central
Keywords: optimize, architecture
Posted-Date: 29 Nov 2008 13:52:37 EST

Hi all


I would like to get any thoughts/experience/suggestion, regarding C
compiler (gcc) for following pipeline processor arch.


We got a "embedded" processor which has one delay slot for any
internal ALU operations and two delay slots for branch and memory load
instructions, see below example. This is due to hardware throughput
requirements. And its resonably easy to schedule instructions to
minimize NOPs when we are doing assembler codes.


However, where I'm a bit clueless is "can we get c compiler (gcc) to
schedule instructions, to minimize NOPs?". Better still "can somone
comment on whats the expected average NOP percentage for such arch,
for a typical C code ?". I know its a very open question and depends
on lots of things.. but any clue/comments are wellcome.


I'm wondering whether to implement hardware resource conflict check or
not. NOPs are not only bubbles in pipeline it increases program memory
foot print and increase power as well, so I need help from high level
language prospective.


Any pointers to reading materials would be much appreciated as well.


Thanks in advance.




ALU instruction, one delay slot
===========


ADD r1 r2 r3
NOP ; required NOP due to ALU delay slot for r1
AND r2 r1 r4


Memory Load instruction, two delay slots
==================


LDW r1 r2
NOP
NOP
ADD r3 r1 r4


Branch instruction, two delay slots
==============


BEQ Lable
NOP ; executed regardless of branch is taken or not
NOP ; executed regardless of branch is taken or not


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.