llvm-svn: 28321

it out of 'ExecutionEngine::create'.  This fixes a problem reported by coverity.

llvm-svn: 28293

object is never deleted though.

llvm-svn: 28256

TargetData.h.  This should make recompiles a bit faster with my current
TargetData tinkering.

llvm-svn: 28238

people aren't reusing machine code buffers at all.

llvm-svn: 28228

Finally, implement ExecutionEngine::freeMachineCodeForFunction.

llvm-svn: 28227

allocation policies and much more.  All this complexity, and we have no
functionality change, woo! :)

llvm-svn: 28225

llvm-svn: 28179

llvm-svn: 28112

llvm-svn: 28087

simplifies the MachineCodeEmitter interface just a little bit and makes
BasicBlocks work like constant pools and jump tables.

llvm-svn: 28082

Refactor TargetMachine, pushing handling of TargetData into the target-specific subclasses.  This has one caller-visible change: getTargetData() now returns a pointer instead of a reference.

This fixes PR 759.

llvm-svn: 28074

llvm-svn: 28073

llvm-svn: 28071

llvm-svn: 28069

llvm-svn: 28066

1. Change several methods in the MachineCodeEmitter class to be pure virtual.
2. Suck emitConstantPool/initJumpTableInfo into startFunction, removing them
   from the MachineCodeEmitter interface, and reducing the amount of target-
   specific code.
3. Change the JITEmitter so that it allocates constantpools and jump tables
   *right* next to the functions that they belong to, instead of in a separate
   pool of memory.  This makes all memory for a function be contiguous, and
   means the JITEmitter only tracks one block of memory now.

llvm-svn: 28065

just have the JIT malloc them.

llvm-svn: 28062

llvm-svn: 28061

code emission location into the base class, instead of being in the derived classes.

This change means that low-level methods like emitByte/emitWord now are no longer
virtual (yaay for speed), and we now have a framework to support growable code
segments.  This implements feature request #1 of PR469.

llvm-svn: 28059

llvm-svn: 28055

llvm-svn: 27967

x86 and ppc for 100% dense switch statements when relocations are non-PIC.
This support will be extended and enhanced in the coming days to support
PIC, and less dense forms of jump tables.

llvm-svn: 27947

This allows Prolangs-C++/city and probably a bunch of other stuff to work
well with the new front-end

llvm-svn: 27941

llvm-svn: 27037

llvm-svn: 26975

llvm-svn: 26971

llvm-svn: 26970

Now you can build a tool with just the JIT or just the interpreter.

llvm-svn: 26946

llvm-svn: 26748

llvm-svn: 26619

llvm-svn: 26079

value/alignment pair for each constant, keep a value/offset pair.

llvm-svn: 26078

llvm-svn: 26076

therefore the function being called must be a main() returning an int.  The
consequences when these assumptions are false are not good, so don't assume
them.

llvm-svn: 26031

interpretation has begun.  The JIT already handles this situation correctly, and
the interpreter can already handle new functions being added.

llvm-svn: 26030

llvm-svn: 25855

llvm-svn: 25516

llvm-svn: 25481

llvm-svn: 25140