1
0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-10-30 07:22:55 +01:00
llvm-mirror/lib/Target/Skeleton
2005-06-25 02:48:37 +00:00
..
.cvsignore ignore generated files 2004-11-21 00:01:54 +00:00
Makefile Change Library Names Not To Conflict With Others When Installed 2004-10-27 23:18:45 +00:00
README.txt Fix grammar. 2004-07-16 17:40:28 +00:00
Skeleton.h Remove trailing whitespace 2005-04-21 23:30:14 +00:00
Skeleton.td Initial checkin of the rest of the skeleton target 2004-07-16 07:11:15 +00:00
SkeletonInstrInfo.cpp Remove trailing whitespace 2005-04-21 23:30:14 +00:00
SkeletonInstrInfo.h Remove trailing whitespace 2005-04-21 23:30:14 +00:00
SkeletonInstrInfo.td Make sure to set the operand list 2004-09-21 17:30:54 +00:00
SkeletonJITInfo.cpp Remove trailing whitespace 2005-04-21 23:30:14 +00:00
SkeletonJITInfo.h Remove trailing whitespace 2005-04-21 23:30:14 +00:00
SkeletonRegisterInfo.cpp Remove trailing whitespace 2005-04-21 23:30:14 +00:00
SkeletonRegisterInfo.h Remove trailing whitespace 2005-04-21 23:30:14 +00:00
SkeletonRegisterInfo.td Revamp the Register class, and allow the use of the RegisterGroup class to 2004-09-14 04:17:02 +00:00
SkeletonTargetMachine.cpp Refactor the addPassesToEmitAssembly interface into a addPassesToEmitFile 2005-06-25 02:48:37 +00:00
SkeletonTargetMachine.h Refactor the addPassesToEmitAssembly interface into a addPassesToEmitFile 2005-06-25 02:48:37 +00:00

LLVM Target Skeleton
--------------------

This directory contains a very simple skeleton that can be used as the
starting point for new LLVM targets.  Basically, you can take this code
and start filling stuff in.

This directory contains mainly stubs and placeholders; there is no binary 
machine code emitter, no assembly writer, and no instruction selector 
here.  Most of the functions in these files call abort() or fail assertions 
on purpose, just to reinforce the fact that they don't work.

The things that are implemented are stubbed out in a pseudo-PowerPC target.
This should give you an idea of what to do, but anything implemented should
be replaced with your target details.

As always, if you're starting a new port, please mention it on the llvmdev
list, and if you have questions, that is a great place to ask.