, Alexander Monakov wrote:
> From: Alexander Monakov
> Subject: Re: pipeline description
> To: "Ian Lance Taylor"
> Cc: "roy rosen" , gcc@gcc.gnu.org
> Date: Friday, November 12, 2010, 1:22 PM
>
>
> On Thu, 11 Nov 2010, Ian Lance Taylor wrote:
>
> >
On Thu, 11 Nov 2010, Ian Lance Taylor wrote:
> roy rosen writes:
>
> > If I have two insns:
> > r2 = r3
> > r3 = r4
> > It seems to me that the dependency analysis creates a dependency
> > between the two and prevent parallelization. Although there is a
> > dependency (because of r3) I want GC
roy rosen writes:
> If I have two insns:
> r2 = r3
> r3 = r4
> It seems to me that the dependency analysis creates a dependency
> between the two and prevent parallelization. Although there is a
> dependency (because of r3) I want GCC to parallelize them together.
> Since if the insns are process
If I have two insns:
r2 = r3
r3 = r4
It seems to me that the dependency analysis creates a dependency
between the two and prevent parallelization. Although there is a
dependency (because of r3) I want GCC to parallelize them together.
Since if the insns are processed together the old value of r3 is
roy rosen writes:
> I am writing now the pipeline description in order to get a parallel code.
> My machine has many restrictions regarding which instruction can be
> parallelized with another.
> I am under the assumption that for each insn only one
> define_insn_reservation is matched.
> Is that
