This is the mail archive of the java-discuss@sourceware.cygnus.com 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]

Re: Array marking

To: Jeff Sturm <jsturm at sigma6 dot com>
Subject: Re: Array marking
From: Tom Tromey <tromey at cygnus dot com>
Date: Sat, 22 Apr 2000 18:35:40 -0700 (PDT)
Cc: Bryce McKinlay <bryce at albatross dot co dot nz>, Tom Tromey <tromey at cygnus dot com>, java-discuss at sourceware dot cygnus dot com
References: <3900EAAE.D9221332@albatross.co.nz><200004220005.RAA23371@ferrule.cygnus.com><390102B0.EFDABE80@albatross.co.nz><390129AC.A41C57C4@sigma6.com>

Jeff> I was wondering too if using GC_malloc_stubborn for known
Jeff> immutable objects (e.g. java.lang.String) could help... or if
Jeff> that is mainly for incremental mode?

I don't know.  One thing to note is that with the current
synchronization implementation, every object is mutable.  This can be
changed (the compiler part of this is done), but nobody has done so.
Synchronization is something that comes up periodically here.  I'd
like to get a chance to do some work on that, but so far it hasn't
happened.

Tom

References:
- Array marking
  - From: Bryce McKinlay
- Re: Array marking
  - From: Tom Tromey
- Re: Array marking
  - From: Bryce McKinlay
- Re: Array marking
  - From: Jeff Sturm

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