is a move between two registers, at least one of the registers is
virtual and the two live intervals do not overlap.

This results in about 40% reduction in intervals, 30% decrease in the
register allocators running time and a 20% increase in peephole
optimizations (mainly move eliminations).

The option can be enabled by passing -join-liveintervals where
appropriate.

llvm-svn: 10965

lives near the other installation dirs (like libdir, bindir, etc.).

Move the rule for making bytecode_libdir out of the ifdef LIBRARYNAME...endif.

llvm-svn: 10964

appropriate "force C++" command-line option.

llvm-svn: 10963

llvm-svn: 10962

llvm-svn: 10961

it's only used in the top-level directory.

llvm-svn: 10960

with the current one.

llvm-svn: 10959

virtReg lives on the stack. Now a virtual register has an entry in the
virtual->physical map or the virtual->stack slot map but never in
both.

llvm-svn: 10958

llvm-svn: 10957

llvm-svn: 10956

map was only used to implement a marginal GlobalsGraph optimization, and it
actually slows the analysis down (due to the overhead of keeping it), so just
eliminate it entirely.

llvm-svn: 10955

llvm-svn: 10954

llvm-svn: 10953

llvm-svn: 10952

in terms of it.

Though clonePartiallyInto is not cloning partial graphs yet, this change
dramatically speeds up inlining of graphs with many scalars.  For example,
this change speeds up the BU pass on 253.perlbmk from 69s to 36s, because
it avoids iteration over the scalar map, which can get pretty large.

llvm-svn: 10951

why this one was)

Add new method proto

llvm-svn: 10950

llvm-svn: 10949

llvm-svn: 10948

llvm-svn: 10947

called bytecode_libdir.  Make install-bytecode-library depend on
the existence of that directory, and add a rule for creating it if
it does not exist by calling mkinstalldirs.

llvm-svn: 10946

llvm-svn: 10945

that are still left in the lazy reader map.

llvm-svn: 10944

their implementation of book-keeping for which functions need to be materialized
and which don't.

llvm-svn: 10943

which ones don't, which is state that the parent class doesn't know without
knowing the implementation. Let the children classes implement
materializeModule().

llvm-svn: 10942

llvm-svn: 10941

llvm-svn: 10940

w.r.t. SHLIBEXT starting with a dot.

:-)

llvm-svn: 10939

llvm-svn: 10938

llvm-svn: 10937

llvm-svn: 10936

llvm-svn: 10935

llvm-svn: 10934

llvm-svn: 10933

llvm-svn: 10932

llvm-svn: 10931

llvm-svn: 10930

llvm-svn: 10929

Fix testcase test/Regression/Assembler/2004-01-20-MaxLongLong.llx

llvm-svn: 10928

it as zero.

llvm-svn: 10927

llvm-svn: 10926