[Gc] mips support broken in gc-7.x
twisti at complang.tuwien.ac.at
Thu May 29 08:19:08 PDT 2008
Since you have already helped me a lot with CACAO on MIPS, could you
have a quick look at this problem? Probably I can fix it myself too,
but I'm not sure.
On Tue, 2008-05-06 at 22:03 +0000, Boehm, Hans wrote:
> Looking at the code, you are clearly correct. I had largely forgotten about that problem. We need at least minimal atomic_ops support for mips. If someone can adapt, for example, cris.h in the atomic_ops-1.2 part of the tree, that should be sufficient for at least basic functionality. I might be able to try, but I'm not sure I still have access to a machine on which I can test.
> There is a bit of a complication here in that it's hard to do this really correctly, we need an accurate description of the MIPS memory consistency model. My understanding is that that's currently more dependent on the individual chip vendor than some of us would like. I have some idea what it should be for old SGI machines, but I suspect that's no longer the primary concern here. I haven't checked on this in a while, so things may be better now.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Christian Thalinger
> Sent: Monday, May 05, 2008 12:38 AM
> To: gc at napali.hpl.hp.com
> Subject: [Gc] mips support broken in gc-7.x
> I want to update to gc-7.x because of some additional functions which are very handy in a JVM. But it seems that MIPS support is broken:
> atomic_ops.c:74: error: parse error before "AO_locks"
> atomic_ops.c:75: error: `AO_TS_CLEAR' undeclared here (not in a function)
> atomic_ops.c:75: error: initializer element is not constant
> atomic_ops.c:75: error: (near initialization for `AO_locks')
> Is MIPS not supported at all anymore or is this just a bug?
> - twisti
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc