didn't handle
X =
Y<dead> = use X
DBG_VALUE(X)
I was hoping to avoid this approach as it's slower,
but I don't think it can be done.

llvm-svn: 95996

2. don't bother trying to merge globals in non-default sections,
   doing so is quite dubious at best anyway.
3. fix a bug reported by Arnaud de Grandmaison where we'd try to
   merge two globals in different address spaces.

llvm-svn: 95995

llvm-svn: 95994

llvm-svn: 95993

with block-pointer-type as one or more of its
arguments. Fixes radar 7638400.

llvm-svn: 95992

within the declarator of another declaration, from Enea Zaffanella!

llvm-svn: 95991

llvm-svn: 95990

llvm-svn: 95989

is breaking llvm-gcc bootstrap.

llvm-svn: 95988

Daniel's suggestion.

llvm-svn: 95987

ASTContext::getFunctionType with the wrong set of arguments.

llvm-svn: 95986

llvm-svn: 95985

llvm-svn: 95984

llvm-svn: 95982

llvm-svn: 95981

This should fix alot of problems we saw so far, e.g. PRs 5851 & 2936

llvm-svn: 95980

doesn't matter, except that ScalarEvolution tends to need less time
to fold the results this way.

llvm-svn: 95979

bug fixes, and with improved heuristics for analyzing foreign-loop
addrecs.

This change also flattens IVUsers, eliminating the stride-oriented
groupings, which makes it easier to work with.

llvm-svn: 95975

* Enabled R1/R2 application for nodes with infinite spill costs in the Briggs heuristic (made
safe by the changes to the normalization proceedure).
* Removed a redundant header.

llvm-svn: 95973

guard macro is already defined for the first occurrence of the
header.  If it is, the body will be skipped and not be properly
analyzed for the include guard optimization.

llvm-svn: 95972

llvm-svn: 95971

Keep track of the address points for all primary bases, and add the ability to dump multiple address points for a single offset.

llvm-svn: 95970

headers, where malloc (and many other libc functions) are declared
with empty throw specifications, e.g.,  

  extern void *malloc (__SIZE_TYPE__ __size) throw () __attribute__
  ((__malloc__)) ;

The C++ standard doesn't seem to allow this, and redeclaring malloc as
the standard permits (as follows) resulted in Clang (rightfully!)
complaining about mis-matched exception specifications.

  void *malloc(size_t size);

We work around this by silently propagating an empty throw
specification "throw()" from a function with C linkage declared in a
system header to a redeclaration that has no throw specifier.

Ick.

llvm-svn: 95969

an overriden type only by reduced qualification.

llvm-svn: 95968

llvm-svn: 95967

  ::__builtin_va_copy

Fixes one of the Firefox issues in PR5511.

llvm-svn: 95966

llvm-svn: 95965

in a single byte-load rather than some crazy bitmunging operation.

llvm-svn: 95964

llvm-svn: 95963

llvm-svn: 95962

This will work better for the disassembler for modeling things
like lfence/monitor/vmcall etc.

llvm-svn: 95960

llvm-svn: 95959

great solution for the disassembler, we'll go with "plan b".

llvm-svn: 95957

matcher is now free of implicit operands!
 - Still need to clean up the code now that we don't to worry about implicit
   operands, and to make it a hard error if an instruction fails to specify all
   of its operands for some reason.

llvm-svn: 95956

MRRC, MRRc2.  For disassembly only.

llvm-svn: 95955

llvm-svn: 95954

llvm-svn: 95953

llvm-svn: 95952

reduce down to a single value.  InstCombine already does this transformation
but DAG legalization may introduce new opportunities.  This has turned out to
be important for ARM where 64-bit values are split up during type legalization:
InstCombine is not able to remove the PHI cycles on the 64-bit values but
the separate 32-bit values can be optimized.  I measured the compile time 
impact of this (running llc on 176.gcc) and it was not significant.

llvm-svn: 95951

with "tied memory operands", which is wrong.

llvm-svn: 95950