Re: [perl #57728] [TODO] avoid 2038 bug if we haven't already.
>> we definitely need date/time pmc(s?) not only to have a common epoch >> across platforms, but to deal with 2038. in particular, we should >> leverage schwern's work on perl to address the 2038 bug. >> ~jerry > > We definitely haven't already fixed this. Here's an easy test using > libfaketime: > > $ cat time.pir > .sub main :main >.local int time_int >time time_int >say time_int > .end > $ ./parrot time.pir > 113121 > $ LD_PRELOAD=/usr/src/libfaketime-0.8/libfaketime.so.1 FAKETIME="+40y" > ./parrot time.pir > -1811314167 We can't make this example work. If you use an INTVAL, and the INTVAL can be signed 32 bits, there is no way to have a more than 31 bits unsigned stored on it as such. -- Salu2
[perl #57728] [TODO] avoid 2038 bug if we haven't already.
On Thu Aug 07 14:20:11 2008, coke wrote: > Open a ticket for TODO item. > > -- Forwarded message -- > From: jerry gay <[EMAIL PROTECTED]> > Date: Thu, Aug 7, 2008 at 4:34 PM > Subject: Re: time op inconsistent on Win32 > To: Ron Blaschke <[EMAIL PROTECTED]> > Cc: Jonathan Worthington <[EMAIL PROTECTED]>, p2 <[EMAIL PROTECTED]> > > we definitely need date/time pmc(s?) not only to have a common epoch > across platforms, but to deal with 2038. in particular, we should > leverage schwern's work on perl to address the 2038 bug. > ~jerry We definitely haven't already fixed this. Here's an easy test using libfaketime: $ cat time.pir .sub main :main .local int time_int time time_int say time_int .end $ ./parrot time.pir 113121 $ LD_PRELOAD=/usr/src/libfaketime-0.8/libfaketime.so.1 FAKETIME="+40y" ./parrot time.pir -1811314167
[perl #57728] [TODO] avoid 2038 bug if we haven't already.
# New Ticket Created by Will Coleda # Please include the string: [perl #57728] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57728 > Open a ticket for TODO item. -- Forwarded message -- From: jerry gay <[EMAIL PROTECTED]> Date: Thu, Aug 7, 2008 at 4:34 PM Subject: Re: time op inconsistent on Win32 To: Ron Blaschke <[EMAIL PROTECTED]> Cc: Jonathan Worthington <[EMAIL PROTECTED]>, p2 <[EMAIL PROTECTED]> we definitely need date/time pmc(s?) not only to have a common epoch across platforms, but to deal with 2038. in particular, we should leverage schwern's work on perl to address the 2038 bug. ~jerry
