For the 4.7 branch I only saw one architecture using exposed pipeline.
Is there any documentation on the quality of exposed pipeline support?
Does the back-end need to do anything special to deal with jumps and
returns from calls?
Thanks
Shmeel
On 11/26/12 12:46, Maxim Kuvyrkov wrote:
> I wonder if "kludgy fixups" refers to the dummy-instruction solution I
> mentioned above. The complete dependence graph is a myth. You cannot have a
> complete dependence graph for a function -- scheduler works on DAG regions
> (and I doubt it will e
On 27/11/2012, at 4:34 AM, Greg McGary wrote:
> On 11/25/12 23:33, Maxim Kuvyrkov wrote:
>> You essentially need a fix-up pass just before the end of compilation
>> (machine-dependent reorg, if memory serves me right) to space instructions
>> consuming values from CPRs from the CALL_INSNS that s
On 11/25/12 23:33, Maxim Kuvyrkov wrote:
> You essentially need a fix-up pass just before the end of compilation
> (machine-dependent reorg, if memory serves me right) to space instructions
> consuming values from CPRs from the CALL_INSNS that set those CPRs. I.e.,
> for the 99% of compilation
On 26/11/2012, at 1:28 PM, Greg McGary wrote:
> I'm working onaport to a VLIW DSP with anexposed pipeline (i.e., no
> interlocks). Some operations OPhave as much as 2-cycle latency on values
> of the call-preserved regs CPR. E.g., if the callee's epiloguerestores a
> CPR in the delay slot of the
I'm working onaport to a VLIW DSP with anexposed pipeline (i.e., no
interlocks). Some operations OPhave as much as 2-cycle latency on values
of the call-preserved regs CPR. E.g., if the callee's epiloguerestores a
CPR in the delay slot of the return instruction, then any OP with that CPR
as input
