Sooooo many of these had incorrect or strange main module includes.
I have manually inspected all of these, and fixed the main module
include to be the nearest plausible thing I could find. If you own or
care about any of these source files, I encourage you to take some time
and check that these edits were sensible. I can't have broken anything
(I strictly added headers, and reordered them, never removed), but they
may not be the headers you'd really like to identify as containing the
API being implemented.

Many forward declarations and missing includes were added to a header
files to allow them to parse cleanly when included first. The main
module rule does in fact have its merits. =]

llvm-svn: 169131

llvm-svn: 143799

While at it, merge some format strings.

llvm-svn: 142140

llvm-svn: 120298

llvm-svn: 110518

llvm-svn: 110516

switch from this:

  if (TimePassesIsEnabled) {
    NamedRegionTimer T(Name, GroupName);
    do_something();
  } else {
    do_something(); // duplicate the code, this time without a timer!
  }

to this:

  {
    NamedRegionTimer T(Name, GroupName, TimePassesIsEnabled);
    do_something();
  }

llvm-svn: 106285

llvm-svn: 104095

llvm-svn: 101376

llvm-svn: 99877

implement TimerGroup::printAll, which prints and resets all active
timers.

llvm-svn: 99876

TimerGroup copy ctor and assignment operator.

llvm-svn: 99875

have it always return a new stream to simplify clients.

llvm-svn: 99874

llvm-svn: 99873

instead of just a count of them, and refactor the guts of
report printing out of removeTimer into its own method.
Refactor addTimerToPrint away.

llvm-svn: 99872

timers by pointer instead of by-value.

llvm-svn: 99871

llvm-svn: 99870

llvm-svn: 99862

llvm-svn: 99842

isn't used by anyone and is better exposed as a non-per-timer 
thing.  Also, stop including System/Mutex.h in Timer.h

llvm-svn: 99841

eliminate the per-timer lock (timers should be 
externally locked if needed), the info-output-stream
can never be dbgs(), so drop the check.  Make some
stuff private.

llvm-svn: 99839

llvm-svn: 99834

llvm-svn: 99831

llvm-svn: 92645

llvm-svn: 89056

llvm-svn: 86347

llvm-svn: 79842

llvm-svn: 74931

Make timers threadsafe again.  This isn't quite as nice as I'd hoped (it uses locking rather than atomic arithmetic),
but should work on all the platforms we care about.

I might revisit this if a totally awesome way to do it occurs to me.

llvm-svn: 74002

we care about are capable of supporting it.

llvm-svn: 73993

llvm-svn: 73988

llvm-svn: 73978

Use 64-bit integer counters for tracking time, rather than doubles.  This will be more atomic op friendly.

llvm-svn: 73974

llvm-svn: 73963

llvm-svn: 73957

llvm-svn: 73923

the BB member to the current basic block after emitting
instructions.

llvm-svn: 53567

llvm-svn: 53502

use a timer group for the timers in SelectionDAGISel. Also,
Split scheduling out from emitting, to give each their own
timer.

llvm-svn: 53476

llvm-svn: 53474