[LLVMdev] ARMSchedule.td MipsSchedule.td etc.

Carter Cheng carter_cheng at yahoo.com
Thu Aug 20 15:07:52 PDT 2009


Thanks. I guess I will ignore it for now. It seems like the current Mips experimental backend doesnt even have this information hooked into the target machine. 

--- On Tue, 8/18/09, David Goodwin <david_goodwin at apple.com> wrote:

> From: David Goodwin <david_goodwin at apple.com>
> Subject: Re: [LLVMdev] ARMSchedule.td MipsSchedule.td etc.
> To: "Carter Cheng" <carter_cheng at yahoo.com>
> Cc: llvmdev at cs.uiuc.edu
> Date: Tuesday, August 18, 2009, 12:23 PM
> Yes. But it is not really being used
> by most (any?) targets because post-RA scheduling is
> disabled by default. Also, the existing model is very
> limited in what types of micro-architectures can be
> described. I've been extending it to enable scheduling of
> multi-issue targets, targets with overlapping FU usage, and
> targets that use and define registers in multiple pipeline
> stages.
> 
> See /include/llvm/Target/TargetInstrItineraries.h for some
> information. The CortexA8Itineraries description in
> ARMScheduleV7.td is where I am using these new features to
> model the Cortex-A8. All of this is a work in progress...
> 
> I suppose when I finish I will write up something
> describing the new Itinerary model and how to use it...
> 
> David
> 
> 
> On Aug 18, 2009, at 1:11 AM, Carter Cheng wrote:
> 
> > Actually after some digging I managed to answer these
> questions for myself. I am guessing that this information is
> used by the Schedule* classes in CodeGen.
> > 
> > --- On Mon, 8/17/09, Carter Cheng <carter_cheng at yahoo.com>
> wrote:
> > 
> >> From: Carter Cheng <carter_cheng at yahoo.com>
> >> Subject: [LLVMdev] ARMSchedule.td MipsSchedule.td
> etc.
> >> To: llvmdev at cs.uiuc.edu
> >> Date: Monday, August 17, 2009, 2:56 PM
> >> I apologize if this has been asked
> >> before but which classes utilize the information
> in these
> >> files? I am asking since I am trying to extend the
> MIPS
> >> backend to 64bit among other things.
> >> 
> >> Thanks in advance,
> >> 
> >> Carter.
> >> 
> >> 
> >> 
> >> 
> >> 
> >> _______________________________________________
> >> LLVM Developers mailing list
> >> LLVMdev at cs.uiuc.edu
> >>        http://llvm.cs.uiuc.edu
> >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> >> 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu 
>        http://llvm.cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> 
> 


      




More information about the llvm-dev mailing list