Bug #26536 func_time failure on vm-win2003-64-b, occurs every time

Description:
*** r/func_time.result	Tue Feb 20 20:01:56 2007
--- r/func_time.reject	Tue Feb 20 20:16:32 2007
***************
*** 561,567 ****
  1970-01-01 03:00:00
  select unix_timestamp(from_unixtime(2147483647));
  unix_timestamp(from_unixtime(2147483647))
! 2147483647
  select unix_timestamp(from_unixtime(2147483648));
  unix_timestamp(from_unixtime(2147483648))
  NULL
--- 561,567 ----
  1970-01-01 03:00:00
  select unix_timestamp(from_unixtime(2147483647));
  unix_timestamp(from_unixtime(2147483647))
! 0
  select unix_timestamp(from_unixtime(2147483648));
  unix_timestamp(from_unixtime(2147483648))
  NULL

How to repeat:
Pushbuild repeats it every time

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/20468

ChangeSet@1.2440, 2007-02-23 17:33:11+01:00, msvensson@pilot.blaudden +2 -0
  Bug#26536 func_time failure on vm-win2003-64-b, occurs every time
   - Avoid overflow in sec_since_epoch by shifting the time
     back 2 days for times close to the maximum range of my_time_t
   - Improve comment about why we need my_time_t
   - Patch will also fix timezone2.test

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/20473

ChangeSet@1.2459, 2007-02-23 17:59:07+01:00, msvensson@pilot.blaudden +1 -0
  Bug#26536 func_time failure on vm-win2003-64-b, occurs every time
   - Fixes for 5.1
   - Always use long for my_time_t

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/20661

ChangeSet@1.2471, 2007-02-27 16:58:40+01:00, msvensson@pilot.blaudden +1 -0
  Bug#26536 func_time failure on vm-win2003-64-b, occurs every time
   - my_time_t is defined as long which means it will not always be the
  same size as time_t. See explanation in include/my_time.h

pushed to 5.0.38, 5.1.17

Noted in 5.0.38, 5.1.17 changelogs.

On 64-bit Windows, large timestamp values could be
handled incorrectly.

Bug #26924 "Test 'timezone2' fails on Windows x64" was marked as duplicate of this bug.