6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-12-21 00:32:23 +00:00
Code Issues Projects Releases Wiki Activity
1f16ff6f0a
llvm-6502/lib/Target/Skeleton
History
Nate Begeman 6510b22cec Support multiple ValueTypes per RegisterClass, needed for upcoming vector 
work.  This change has no effect on generated code.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@24563 91177308-0d34-0410-b5e6-96231b3b80d8
2005-12-01 04:51:06 +00:00
..
.cvsignore
Makefile
README.txt
Skeleton.h
Skeleton.td CR registers are not used by this "target" 2005-09-30 06:43:58 +00:00
SkeletonInstrInfo.cpp
SkeletonInstrInfo.h
SkeletonInstrInfo.td
SkeletonJITInfo.cpp
SkeletonJITInfo.h
SkeletonRegisterInfo.cpp Pass extra regclasses into spilling code 2005-09-30 01:29:42 +00:00
SkeletonRegisterInfo.h Pass extra regclasses into spilling code 2005-09-30 01:29:42 +00:00
SkeletonRegisterInfo.td Support multiple ValueTypes per RegisterClass, needed for upcoming vector 2005-12-01 04:51:06 +00:00
SkeletonTargetMachine.cpp Add a new option to indicate we want the code generator to emit code quickly,not spending tons of time microoptimizing it. This is useful for an -O0style of build. 2005-11-08 02:11:51 +00:00
SkeletonTargetMachine.h Add a new option to indicate we want the code generator to emit code quickly,not spending tons of time microoptimizing it. This is useful for an -O0style of build. 2005-11-08 02:11:51 +00:00

README.txt 

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.