Boost C++ Libraries: Ticket #2809: [patch] Date Time exception with MinGW

attachment set

bley@… — Fri, 27 Feb 2009 15:41:09 GMT

attachment → datetime_mingw_convert_exception.diff

component changed; owner set

Steven Watanabe — Fri, 27 Feb 2009 17:36:48 GMT

owner set to az_sw_dude
component None → date_time

anonymous — Thu, 05 Mar 2009 15:42:03 GMT

As noted by Bruno Dutra on the Boost Users mailing list ("Exception: could not convert calendar time to UTC time"), the exception problem can be solved by replacing the type of the variable micros by std::time_t (boost/date_time/microsec_time_clock.hpp, revision 49874, line 90).

Claudio Bley — Mon, 09 Mar 2009 09:42:32 GMT

Hi.

Replying to anonymous:

As noted by Bruno Dutra on the Boost Users mailing list ("Exception: could not convert calendar time to UTC time"), the exception problem can be solved by replacing the type of the variable micros by std::time_t (boost/date_time/microsec_time_clock.hpp, revision 49874, line 90).

Granted, this prevents the exception -- but microsec_clock::create_time() returns entirely wrong results.

cout << boost::posix_time::microsec_clock::local_time() << endl;

Result:

1970-Jan-01 01:43:38.138948

And, no, my system date is not set to 1970-Jan-01. ;)

Regards, Claudio

anonymous — Wed, 06 May 2009 14:47:26 GMT

Will Claudio's patch be included in the next release? Using the patch on my Windows CP machine and MinGW works like a charm.

anonymous — Wed, 06 May 2009 14:48:54 GMT

Replying to anonymous:

Will Claudio's patch be included in the next release? Using the patch on my Windows CP machine and MinGW works like a charm.

Sorry for the typo, should be Windows XP.

christian.stimming@… — Wed, 13 May 2009 18:53:10 GMT

I can confirm both the problem (mingw, gcc-3.4.2) and its proposed solution. As an alternative to the patch above, the change below would fix the warning as well. Please please include it in SVN, thanks a lot!

--- filetime_functions.hpp~     Wed May 13 12:13:16 2009
+++ filetime_functions.hpp      Wed May 13 18:35:09 2009
@@ -98,7 +98,7 @@
         * in 100-nanosecond intervals */
         const uint64_t c1 = 27111902UL;
         const uint64_t c2 = 3577643008UL; // issues warning without 'UL'
-        const uint64_t shift = (c1 << 32) + c2;
+        const uint64_t shift = (uint64_t(c1) << 32) + c2;
         union {
             FileTimeT as_file_time;

Claudio Bley — Wed, 27 May 2009 06:54:17 GMT

Replying to christian.stimming@ibeo-as.com:

As an alternative to the patch above, the change below would fix the warning as well.

I can't confirm that your patch works. Contrary, I still get the warning as well as the exception.

Regards, Claudio

status changed; resolution set

Andrey Semashev — Thu, 04 Jun 2009 10:07:44 GMT

status new → closed
resolution → fixed

(In [53622]) Fixes #2809.

Andrey Semashev — Sat, 06 Jun 2009 11:24:11 GMT

(In [53677]) Fixes #2809.