Allow the use of the optimized used timers
Cleanup the AMD64 timer function.
Minor cleanups.
Allow for native timer (cycle level) integration
for MPI_Wtime and MPI_Wtick.
Reenable the integration of OPAL level timers with
MPI_Wtime and MPI_Wtick.
Merge branch 'topic/accurate_timers'
Remove useless header.
Per Dave suggestion add a serializing instruction bundled
together with RDTSC. It is still not perfect, but hopefully
much better than before.
On Darwin make sure the field we expect to be 0 is indeed 0.
Cleanup the clobber list.
Improved support for OSX timers.
The use of cpuid destroys the content of %eax and %edx,
so they must be saved before.
Merge branch 'master' of github.com:open-mpi/ompi
Some minor cleanup. We really don't need another peer error constant to indicate that a peer closed as we already have one for "connection failed", and that's all we really know. Update the orte constants to track their opal equivalents.
Merge pull request #285 from bosilca/master

Reenable high accuracy timers
fixes for direct routed component under mpirun
Use RDTSC by now.
Only use RDTSCP if supported by the processor.

Conflicts:
	opal/include/opal/sys/amd64/timer.h
Adding of missed time measurement scripts in tarball
Merge pull request #291 from nkogteva/master

Adding of missed time measurement scripts in tarball
ompi_proc_finalize has an interesting side effect. A proc is
inserted in the ompi_proc_list as soon as it is created and it
is removed only upon the call to the destructor. In ompi_proc_finalize
we loop over all procs in ompi_proc_finalize and release them once.
However, as a proc is not removed from this list right away, we
decrease the ref count for each proc until it reach zero and the
proc is finally removed. Thus, we cannot clean the BML/BTL after
the call the ompi_proc_finalize.
A quick fix is to delay the call to ompi_proc_finalize until all
other frameworks have been finalized, and then the behavior
depicted above will give the expected outcome.