On Fri, Feb 23, 2007 at 07:00:01AM -0800, Ian Lance Taylor wrote:
> gcc currently does a relatively crummy job of handling this type of
> VLIW architecture. You can describe the dependencies in the
> scheduler, but the scheduler won't insert any required nops for you.
> The usual approach is walk
Paul Brook <[EMAIL PROTECTED]> writes:
> > > 1. Is there a way to check for dependency b/w this two instructions.
> > > 2. Any existing backend that has this type of design.
> >
> > gcc currently does a relatively crummy job of handling this type of
> > VLIW architecture. You can describe the dep
> > 1. Is there a way to check for dependency b/w this two instructions.
> > 2. Any existing backend that has this type of design.
>
> gcc currently does a relatively crummy job of handling this type of
> VLIW architecture. You can describe the dependencies in the
> scheduler, but the scheduler wo
"Rohit Arul Raj" <[EMAIL PROTECTED]> writes:
> I am adding floating point support to GCC 4.1.1 for a private target.
>
> My machine can issue
> (1) Two instructions, [one integer insns (16 bit) + one floating point
> insn (16 bit) ]or
> (2) one 32 bit integer insn.
>
> For case (1) , Since both
Hi all,
I am adding floating point support to GCC 4.1.1 for a private target.
My machine can issue
(1) Two instructions, [one integer insns (16 bit) + one floating point
insn (16 bit) ]or
(2) one 32 bit integer insn.
For case (1) , Since both instructions are executed parallely, there
is no dep
