Right. I was mainly wondering if it was worth prototyping a GC in the
jikes/RVM infrastructure. On the one hand I could do comparative
measurement. On the other I can get measurements of existing contributed
GCs on modern machines.

I pulled the tree using mercurial (they seem to have switched). I'm not
convinced that it's maintained.


On Wed, Oct 16, 2013 at 8:36 PM, William ML Leslie <
[email protected]> wrote:

> On 17 October 2013 14:10, Jonathan S. Shapiro <[email protected]> wrote:
> > Lots of benchmarks using this infrastructure, many of them old by now.
> Might
> > be interesting to re-run on newer hardware.
> >
> > Does anyone know the status of jikes/RVM? Is it still runnable? Has it
> been
> > maintained?
>
> I sit opposite an inactive core contributor, so I asked him.
>
> It's still pretty active in the research community, a fork (which?) of
> the compiler generates good code (he claims it outperforms the latest
> hotspot), MMTk rocks &c.  But it moves pretty slowly in terms of
> infrastructure; the website mentions that it doesn't support "64 bit
> Intel" (as much as I wish that IA64 was a thing I think they mean
> x86_64, is worth a try) and I don't even know if they support Java 6.
>
> I've come to work today without the disk that has my JikesRVM build
> environment on it, otherwise I'd let you know with more confidence;
> that said I haven't given it an "svn up" in at least three years.
>
> --
> William Leslie
>
> Notice:
> Likely much of this email is, by the nature of copyright, covered
> under copyright law.  You absolutely may reproduce any part of it in
> accordance with the copyright law of the nation you are reading this
> in.  Any attempt to deny you those rights would be illegal without
> prior contractual agreement.
> _______________________________________________
> bitc-dev mailing list
> [email protected]
> http://www.coyotos.org/mailman/listinfo/bitc-dev
>
>
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to