This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

GC / GCJ / and binutils (ld)


Peter Blemel writes:
 > The macros in GCJ (specifically MS_TIME_DIFF) seem to ignore the fact that a 
 > DWORD tick count even expressed in millis will wrap around every 49.7 days 
 > (E.g. MS Windows).   This is a problem if garbage collection is running 
 > right about that time, because attempts to limit the time used by GC will 
 > not be successful if the clock 'rolls over' during GC.   It's not terribly 
 > unusual for an embedded application to run for this long, and in the 
 > (unlikely) event that this occurs, the application will stop until gc 
 > completes.

Why will there be a problem?  Even when the tick count wraps around,
the time difference should still be correct.  Mind you, I don't know
exactly what GetTickCount() does.

Andrew.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]