llvm-svn: 63527

llvm-svn: 63523

llvm-svn: 63498

crashes or wrong code with codegen of large integers:
eliminate the legacy getIntegerVTBitMask and
getIntegerVTSignBit methods, which returned their
value as a uint64_t, so couldn't handle huge types.

llvm-svn: 63494

llvm-svn: 63493

llvm-svn: 63492

Fix an issue in PHI construction that was exposed by GCC 4.2 producing a different set iteration order for the reg_iterator.

llvm-svn: 63490

llvm-svn: 63488

llvm-svn: 63486

llvm-svn: 63485

returned by getShiftAmountTy may be too small
to hold shift values (it is an i8 on x86-32).
Before and during type legalization, use a large
but legal type for shift amounts: getPointerTy;
afterwards use getShiftAmountTy, fixing up any
shift amounts with a big type during operation
legalization.  Thanks to Dan for writing the
original patch (which I shamelessly pillaged).

llvm-svn: 63482

when A==B, -0.0 != +0.0.

llvm-svn: 63474

llvm-svn: 63473

llvm-svn: 63468

Complete (modulo bugs).

llvm-svn: 63458

(modulo bugs)

llvm-svn: 63457

couple of things that use it.

llvm-svn: 63456

llvm-svn: 63454

llvm-svn: 63452

llvm-svn: 63451

llvm-svn: 63446

argument.  Adjust all callers and overloaded versions.

llvm-svn: 63444

llvm-svn: 63443

llvm-svn: 63442

llvm-svn: 63441

llvm-svn: 63440

llvm-svn: 63439

llvm-svn: 63437

llvm-svn: 63436

llvm-svn: 63434

llvm-svn: 63433

- Added xform for (select X, 1, Y) and (select X, Y, 0), which was commented on,
  but missing.

llvm-svn: 63428

llvm-svn: 63424

llvm-svn: 63420

llvm-svn: 63419

llvm-svn: 63417

llvm-svn: 63416

llvm-svn: 63411

 Each input file is encoded as a separate compile unit in LLVM debugging
information output. However, many target specific tool chains prefer to encode
only one compile unit in an object file. In this situation, the LLVM code
generator will include  debugging information entities in the compile unit 
that is marked as main compile unit. The code generator accepts maximum one main
compile unit per module. If a module does not contain any main compile unit 
then the code generator will emit multiple compile units in the output object 
file.

[Part 1]

Update DebugInfo APIs to accept optional boolean value while creating DICompileUnit  to mark the unit as "main" unit. By defaults all units are considered  non-main.  Update SourceLevelDebugging.html to document "main" compile unit.

Update DebugInfo APIs to not accept and encode separate source file/directory entries while creating various llvm.dbg.* entities. There was a recent, yet to be documented, change to include this additional information so no documentation changes are required here.

Update DwarfDebug to handle "main" compile unit. If "main" compile unit is seen then all DIEs are inserted into "main" compile unit. All other compile units are used to find source location for llvm.dbg.* values. If there is not any "main" compile unit then create unique compile unit DIEs for each llvm.dbg.compile_unit.

[Part 2]

Create separate llvm.dbg.compile_unit for each input file. Mark compile unit create for main_input_filename as "main" compile unit. Use appropriate compile unit, based on source location information collected from the tree node, while creating llvm.dbg.* values using DebugInfo APIs.

---

This is Part 1.

llvm-svn: 63400

Thanks, Duncan.

llvm-svn: 63389