Swiftdiff options
| author | Tobias Markmann <tm@ayena.de> | 2014-10-19 20:22:58 (GMT) |
|---|---|---|
| committer | Tobias Markmann <tm@ayena.de> | 2014-10-20 13:49:33 (GMT) |
| commit | 6b22dfcf59474dd016a0355a3102a1dd3692d92c (patch) | |
| tree | 2b1fd33be433a91e81fee84fdc2bf1b52575d934 /3rdParty/Boost/src/boost/chrono/system_clocks.hpp | |
| parent | 38b0cb785fea8eae5e48fae56440695fdfd10ee1 (diff) | |
| download | swift-contrib-6b22dfcf59474dd016a0355a3102a1dd3692d92c.zip swift-contrib-6b22dfcf59474dd016a0355a3102a1dd3692d92c.tar.bz2 | |
Update Boost in 3rdParty to version 1.56.0.
This updates Boost in our 3rdParty directory to version 1.56.0.
Updated our update.sh script to stop on error.
Changed error reporting in SwiftTools/CrashReporter.cpp to SWIFT_LOG due to
missing include of <iostream> with newer Boost.
Change-Id: I4b35c77de951333979a524097f35f5f83d325edc
Diffstat (limited to '3rdParty/Boost/src/boost/chrono/system_clocks.hpp')
| -rw-r--r-- | 3rdParty/Boost/src/boost/chrono/system_clocks.hpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/3rdParty/Boost/src/boost/chrono/system_clocks.hpp b/3rdParty/Boost/src/boost/chrono/system_clocks.hpp index df8b79e..5ba6a3b 100644 --- a/3rdParty/Boost/src/boost/chrono/system_clocks.hpp +++ b/3rdParty/Boost/src/boost/chrono/system_clocks.hpp @@ -35,71 +35,71 @@ TODO: > In the past I've seen QueryPerformanceCounter give incorrect results, > especially with SpeedStep processors on laptops. This was many years ago and > might have been fixed by service packs and drivers. > > Typically you check the results of QPC against GetTickCount to see if the > results are reasonable. > http://support.microsoft.com/kb/274323 > > I've also heard of problems with QueryPerformanceCounter in multi-processor > systems. > > I know some people SetThreadAffinityMask to 1 for the current thread call > their QueryPerformance* functions then restore SetThreadAffinityMask. This > seems horrible to me because it forces your program to jump to another > physical processor if it isn't already on cpu0 but they claim it worked well > in practice because they called the timing functions infrequently. > > In the past I have chosen to use timeGetTime with timeBeginPeriod(1) for > high resolution timers to avoid these issues. */ #ifndef BOOST_CHRONO_SYSTEM_CLOCKS_HPP #define BOOST_CHRONO_SYSTEM_CLOCKS_HPP #include <boost/chrono/config.hpp> #include <boost/chrono/duration.hpp> #include <boost/chrono/time_point.hpp> #include <boost/chrono/detail/system.hpp> #include <boost/chrono/clock_string.hpp> #include <ctime> # if defined( BOOST_CHRONO_POSIX_API ) -# if ! defined(CLOCK_REALTIME) +# if ! defined(CLOCK_REALTIME) && ! defined (__hpux__) # error <time.h> does not supply CLOCK_REALTIME # endif # endif #ifdef BOOST_CHRONO_WINDOWS_API // The system_clock tick is 100 nanoseconds # define BOOST_SYSTEM_CLOCK_DURATION boost::chrono::duration<boost::int_least64_t, ratio<BOOST_RATIO_INTMAX_C(1), BOOST_RATIO_INTMAX_C(10000000)> > #else # define BOOST_SYSTEM_CLOCK_DURATION boost::chrono::nanoseconds #endif // this must occur after all of the includes and before any code appears: #ifndef BOOST_CHRONO_HEADER_ONLY #include <boost/config/abi_prefix.hpp> // must be the last #include #endif //----------------------------------------------------------------------------// // // // 20.9 Time utilities [time] // // synopsis // // // //----------------------------------------------------------------------------// namespace boost { namespace chrono { // Clocks class BOOST_CHRONO_DECL system_clock; #ifdef BOOST_CHRONO_HAS_CLOCK_STEADY class BOOST_CHRONO_DECL steady_clock; #endif #ifdef BOOST_CHRONO_HAS_CLOCK_STEADY typedef steady_clock high_resolution_clock; // as permitted by [time.clock.hires] |