llvm-6502/lib/Target/MSP430
Chris Lattner 6c2f9e14fd eliminate AsmPrinter::SwitchToSection and just have clients
talk to the MCStreamer directly instead.


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@79405 91177308-0d34-0410-b5e6-96231b3b80d8
2009-08-19 05:49:37 +00:00
..
AsmPrinter eliminate AsmPrinter::SwitchToSection and just have clients 2009-08-19 05:49:37 +00:00
TargetInfo Factor commonality in triple match routines into helper template for registering 2009-07-26 05:03:33 +00:00
CMakeLists.txt Hopefully unbreak cmake builds 2009-08-14 18:46:49 +00:00
Makefile Give MSP430 a separate asmprinter lib 2009-08-14 18:28:12 +00:00
MSP430.h Add new helpers for registering targets. 2009-07-25 06:49:55 +00:00
MSP430.td
MSP430CallingConv.td
MSP430InstrFormats.td
MSP430InstrInfo.cpp llvm_unreachable->llvm_unreachable(0), LLVM_UNREACHABLE->llvm_unreachable. 2009-07-14 16:55:14 +00:00
MSP430InstrInfo.h
MSP430InstrInfo.td Special constants as destinations does not work as expected - drop the patterns. 2009-08-05 14:42:00 +00:00
MSP430ISelDAGToDAG.cpp Split EVT into MVT and EVT, the former representing _just_ a primitive type, while 2009-08-11 20:47:22 +00:00
MSP430ISelLowering.cpp Split EVT into MVT and EVT, the former representing _just_ a primitive type, while 2009-08-11 20:47:22 +00:00
MSP430ISelLowering.h Major calling convention code refactoring. 2009-08-05 01:29:28 +00:00
MSP430MachineFunctionInfo.h Add explicit keywords. 2009-06-05 23:05:51 +00:00
MSP430RegisterInfo.cpp Give getPointerRegClass() a "kind" value so that targets can 2009-07-29 20:31:52 +00:00
MSP430RegisterInfo.h Give getPointerRegClass() a "kind" value so that targets can 2009-07-29 20:31:52 +00:00
MSP430RegisterInfo.td
MSP430Subtarget.cpp Normalize Subtarget constructors to take a target triple string instead of 2009-08-02 22:11:08 +00:00
MSP430Subtarget.h Normalize Subtarget constructors to take a target triple string instead of 2009-08-02 22:11:08 +00:00
MSP430TargetAsmInfo.cpp Change TargetAsmInfo to be constructed via TargetRegistry from a Target+Triple 2009-08-12 07:22:17 +00:00
MSP430TargetAsmInfo.h Change TargetAsmInfo to be constructed via TargetRegistry from a Target+Triple 2009-08-12 07:22:17 +00:00
MSP430TargetMachine.cpp Cleanup the mess in msp430 target registration and hopefully unbreak the build 2009-08-14 19:06:50 +00:00
MSP430TargetMachine.h Change TargetAsmInfo to be constructed via TargetRegistry from a Target+Triple 2009-08-12 07:22:17 +00:00
README.txt

//===---------------------------------------------------------------------===//
// MSP430 backend.
//===---------------------------------------------------------------------===//

DISCLAIMER: Thid backend should be considered as highly experimental. I never
seen nor worked with this MCU, all information was gathered from datasheet
only. The original intention of making this backend was to write documentation
of form "How to write backend for dummies" :) Thes notes hopefully will be
available pretty soon.

Some things are incomplete / not implemented yet (this list surely is not
complete as well):

0. Implement asmprinting for variables :)

1. Verify, how stuff is handling implicit zext with 8 bit operands (this might
be modelled currently in improper way - should we need to mark the superreg as
def for every 8 bit instruction?).

2. Libcalls: multiplication, division, remainder. Note, that calling convention
for libcalls is incomptible with calling convention of libcalls of msp430-gcc
(these cannot be used though due to license restriction).

3. Implement multiplication / division by constant (dag combiner hook?).

4. Implement non-constant shifts.

5. Implement varargs stuff.

6. Verify and fix (if needed) how's stuff playing with i32 / i64.

7. Implement floating point stuff (softfp?)

8. Implement instruction encoding for (possible) direct code emission in the
future.

9. Since almost all instructions set flags - implement brcond / select in better
way (currently they emit explicit comparison).

10. Handle imm in comparisons in better way (see comment in MSP430InstrInfo.td)

11. Implement hooks for better memory op folding, etc.