This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: java.util.Timer not handling negative System.currentTimeMillis()
- From: Tom Tromey <tromey at redhat dot com>
- To: Martin Egholm Nielsen <martin at egholm-nielsen dot dk>
- Cc: java at gcc dot gnu dot org
- Date: Thu, 24 Nov 2005 17:18:36 -0700
- Subject: Re: java.util.Timer not handling negative System.currentTimeMillis()
- References: <dlhkm9$t7o$1@sea.gmane.org>
- Reply-to: tromey at redhat dot com
>>>>> "Martin" == Martin Egholm Nielsen <martin@egholm-nielsen.dk> writes:
Martin> I know this is an obscure problem, but is there is requirement
Martin> that we are only "allowed" to run gcj on targets with clocks >
Martin> 1970.
The portability code isn't fully spec'd out to this level. The code
is the only guide.
Martin> For now I will just make sure the time is not less than 1970
Martin> and larger than some other limit overflowing the long.
Martin> The problem arises because my target's RTC comes with an undefinded
Martin> initial time - hence anything is possible :-)
Yeah, you should probably initialize this sometime before initializing
libgcj. It seems to me that this randomness would preclude a workable
libgcj patch... ?
Tom