search for: nextcycles

Displaying 8 results from an estimated 8 matches for "nextcycles".

2011 Oct 06
3
[LLVMdev] Multiple-Pipeline Itinerary
Is there a way to express a multiple pipeline itinerary using the current scheme (maybe some trick with setting NextCycles = 0)? Specifically, consider a case where a floating-point load simultaneously uses units from a floating-point pipeline and a load/store pipeline. Thanks in advance, Hal -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory
2011 Oct 06
0
[LLVMdev] Multiple-Pipeline Itinerary
Hello Hal. > Is there a way to express a multiple pipeline itinerary using the > current scheme Yes, surely > (maybe some trick with setting NextCycles = 0)? Yep! > Specifically, consider a case where a floating-point load simultaneously > uses units from a floating-point pipeline and a load/store pipeline. Look into ARM itineraries, they contain a decent amount of such examples. -- With best regards, Anton Korobeynikov Faculty of Mathema...
2013 Feb 12
2
[LLVMdev] DFAPacketizer
...> Jonas > > /Thu Oct 6 15:11:25 CDT 2011:/ > > // > > /Hello Hal./ > > // > > /> Is there a way to express a multiple pipeline itinerary using the/ > > /> current scheme/ > > /Yes, surely/ > > // > > /> (maybe some trick with setting NextCycles = 0)?/ > > /Yep!/ > > // > > /> Specifically, consider a case where a floating-point load > simultaneously/ > > /> uses units from a floating-point pipeline and a load/store pipeline./ > > /Look into ARM itineraries, they contain a decent amount of such >...
2013 Feb 12
0
[LLVMdev] DFAPacketizer
...e is this a temporary deficiency in the DFAPacketizer? What is the IIC_iMOVi itinerary doing below? Thanks, Jonas Thu Oct 6 15:11:25 CDT 2011: Hello Hal. > Is there a way to express a multiple pipeline itinerary using the > current scheme Yes, surely > (maybe some trick with setting NextCycles = 0)? Yep! > Specifically, consider a case where a floating-point load simultaneously > uses units from a floating-point pipeline and a load/store pipeline. Look into ARM itineraries, they contain a decent amount of such examples. [Head feb 2013:] InstrItinData<IIC_iMOVi , [InstrStage&...
2013 Feb 11
2
[LLVMdev] DFAPacketizer
Jonas, At this point, the DFA packetizer models a simple VLIW architecture and does not accommodate multiple stages. That's the reason for the behavior you're seeing. -Anshu --- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation *From:*llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] *On Behalf Of *Jonas
2013 Feb 18
0
[LLVMdev] DFAPacketizer
...e is this a temporary deficiency in the DFAPacketizer? What is the IIC_iMOVi itinerary doing below? Thanks, Jonas Thu Oct 6 15:11:25 CDT 2011: Hello Hal. > Is there a way to express a multiple pipeline itinerary using the > current scheme Yes, surely > (maybe some trick with setting NextCycles = 0)? Yep! > Specifically, consider a case where a floating-point load simultaneously > uses units from a floating-point pipeline and a load/store pipeline. Look into ARM itineraries, they contain a decent amount of such examples. [Head feb 2013:] InstrItinData<IIC_iMOVi , [InstrStage&...
2011 Oct 06
2
[LLVMdev] Multiple-Pipeline Itinerary
...e difference between Reserved and Required? -Hal On Fri, 2011-10-07 at 00:11 +0400, Anton Korobeynikov wrote: > Hello Hal. > > > Is there a way to express a multiple pipeline itinerary using the > > current scheme > Yes, surely > > > (maybe some trick with setting NextCycles = 0)? > Yep! > > > Specifically, consider a case where a floating-point load simultaneously > > uses units from a floating-point pipeline and a load/store pipeline. > Look into ARM itineraries, they contain a decent amount of such examples. -- Hal Finkel Postdoctoral Appoin...
2011 Oct 22
0
[LLVMdev] Instruction Scheduling Itineraries
...ion stage - These values represent a non-pipelined step in // the execution of an instruction. Cycles represents the number of // discrete time slots needed to complete the stage. Units represent // the choice of functional units that can be used to complete the // stage. Eg. IntUnit1, IntUnit2. NextCycles indicates how many // cycles should elapse from the start of this stage to the start of // the next stage in the itinerary. For example: // // A stage is specified in one of two ways: // // InstrStage<1, [FU_x, FU_y]> - TimeInc defaults to Cycles // InstrStage<1, [FU_x, FU_y], 0&g...