sablevm-developer

[Sablevm-developer] SableVM/Solaris status report request

[Grzegorz B. P. <ga...@de...>]

Hi guys!

AFAIK there were some problems w/ Solaris port of SableVM, like:
- you had to fix libffi,
- in classpath you changed file longint to standard int (which
would suggest that 64-bit value handling was broken?)

Have the libffi fixes for Solaris been pushed upstream?
Where's the diff of them?

Have the problem w/ 64-bit values been fixed?

Does SableVM on Solaris run BTS tests properly on all engines?

Are there any other problems I ommited above?

Is there anything missing so that one could simply checkout SableVM and
GNU Classpath from SVN/staging and compile it (and run/use) on Solaris?

I'd be interested in hearing what are the plans regarding this port,
and how do you feel about its current state.

Thanks in advance,

				Grzegorz B. Prokopski

-- 
Grzegorz B. Prokopski <ga...@de...>
Debian GNU/Linux      http://www.debian.org
SableVM - LGPLed JVM  http://www.sablevm.org
Why SableVM ?!?       http://devel.sablevm.org/wiki/WhySableVM

[Sablevm-developer] Re: SableVM/Solaris status report request

[David <db...@CS...>]

On Sun, Feb 08, 2004 at 02:48:46AM -0500, Grzegorz B. Prokopski wrote:
> Hi guys!
>=20

Hi Greg,

> AFAIK there were some problems w/ Solaris port of SableVM, like:
> - you had to fix libffi,

yes.

> - in classpath you changed file longint to standard int (which
> would suggest that 64-bit value handling was broken?)

I remember at the beginning we had to change a few 64-bit int
to 32-bit int.  But these should be no longer necessary.

> Have the libffi fixes for Solaris been pushed upstream?
> Where's the diff of them?
>=20

If I remember well for libffi, we took and maybe modified part of the
newer version into an older version.  We will need to have a look again
at that with a recent libffi and send the diff upstream.


> Have the problem w/ 64-bit values been fixed?
>=20

Yes.

> Does SableVM on Solaris run BTS tests properly on all engines?
>=20
> Are there any other problems I ommited above?
>=20
> Is there anything missing so that one could simply checkout SableVM and
> GNU Classpath from SVN/staging and compile it (and run/use) on Solaris?
>=20
> I'd be interested in hearing what are the plans regarding this port,
> and how do you feel about its current state.

I will let Christian comment on this part, I don't know which change
was done in SableVM and if they have been pushed to staging.


Note: Next week we will merge my most recent SableVM/SableJIT changes
      into Christian branch.  At that point, we could check diffs
      and push SableVM changes, if any, to staging.


David

---

David B=E9langer
Graduate Student
School of Computer Science
McGill University
Office: MC226

Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt

[Sablevm-developer] Re: SableVM/Solaris status report request

[David <db...@cs...>]

On Sun, Feb 08, 2004 at 11:35:23AM -0500, David B=E9langer wrote:
> On Sun, Feb 08, 2004 at 02:48:46AM -0500, Grzegorz B. Prokopski wrote:
> > Hi guys!
> >=20
>=20
> Hi Greg,
>=20
> > AFAIK there were some problems w/ Solaris port of SableVM, like:
> > - you had to fix libffi,
>=20
> yes.

Hi,

Small update for Solaris/sparc.

libffi - Tried again with snapshot extracted from pyobjc project.
         Not working, looks syntax errors in assembly file.
Will study/fix that later.

> > - in classpath you changed file longint to standard int (which
> > would suggest that 64-bit value handling was broken?)
>=20
> I remember at the beginning we had to change a few 64-bit int
> to 32-bit int.  But these should be no longer necessary.
>=20

Classpath/staging almost works for Solaris/sparc.
2 issues:
- need extra include for a #define constants.
- does not compile doc
See patch attached.

> > Have the libffi fixes for Solaris been pushed upstream?
> > Where's the diff of them?
> >=20
>=20
> If I remember well for libffi, we took and maybe modified part of the
> newer version into an older version.  We will need to have a look again
> at that with a recent libffi and send the diff upstream.
>=20

Will look into that later.

>=20
> > Have the problem w/ 64-bit values been fixed?
> >=20
>=20
> Yes.
>=20

SableVM bootstraps and runs HelloWorld kind of programs.  Did not
heavily test.  64-bit problem seems ok with old modified libffi.

No changes are required in SableVM.

Did not run the BTS yet.

Help for SableVM/Solaris welcome.


David

---

David B=E9langer
Graduate Student
School of Computer Science
McGill University
Office: MC226

Web page:   http://www.cs.mcgill.ca/~dbelan2/
Public key: http://www.cs.mcgill.ca/~dbelan2/public_key.txt