Re: [hatari-devel] Time overflow patch |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Time overflow patch
- From: David Savinkoff <dsavnkff@xxxxxxxxx>
- Date: Sun, 3 Nov 2013 12:03:29 -0700 (MST)
- Thread-index: KnKAMozz9/0H9rozFIsSLL/BnPy8pA==
- Thread-topic: Time overflow patch
----- Thomas Huth wrote:
> Hi,
>
> Am Sun, 3 Nov 2013 01:13:51 -0600 (MDT)
> schrieb David Savinkoff <dsavnkff@xxxxxxxxx>:
> >
> > Hi Thomas,
> >
> > I'm withdrawing the previous patch 'time.overflow.diff'
> > because of a new problem that it doesn't address.
> >
> > Please apply time.overflow3.diff.
> >
> > I found that I can freeze Hatari by setting my system
> > clock backwards after Hatari is started.
> >
> > 1) Start Hatari and move mouse around.
> > 2) date --set='-15 minutes'
> > 3) Note Hatari is frozen
> > 4) date --set='+15 minutes'
> > 5) Note Hatari is Ok
> >
> > Hatari did not appear to have delays due to the variables wrapping,
> > however, it does when the time is set backwards. When Sint32
> > variables are used, the delay is aliased on 71.58 minutes.
> >
> > time.overflow2.diff is the 'test patch' using Sint32 variables
> > that wrap in 71.58 minutes. Both time.overflow2.diff and
> > time.overflow3.diff fix the freezing problem.
>
> Ok, thanks for the description, I fixed it now, but slightly different
> than in your patch (without introducing another variable). Please test
> whether that fixes the problem for you, too.
>
> Thomas
>
Tested ok; even with Sint64 variables changed to Sint32 and
altering the system clock while the MUDA demo was running.
Also, no anomalies during an additional 45 minute run with
Sint64 variables changed to Sint32 and the system clock
set properly without modification during the run.
David