sablevm-developer Mailing List for SableVM (Page 20)
Brought to you by:
egagnon
Menu
▾
▴
sablevm-developer — SableVM developer mailing list
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(27) |
Aug
(22) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(30) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(32) |
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(69) |
Sep
(10) |
Oct
(31) |
Nov
(15) |
Dec
(58) |
| 2003 |
Jan
(33) |
Feb
(81) |
Mar
(85) |
Apr
(24) |
May
(15) |
Jun
(14) |
Jul
(6) |
Aug
(9) |
Sep
(101) |
Oct
(59) |
Nov
(142) |
Dec
(34) |
| 2004 |
Jan
(107) |
Feb
(164) |
Mar
(181) |
Apr
(96) |
May
(81) |
Jun
(71) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-19 05:29:44
|
Hi all, I am leaving tomorrow afternoon. I hope to have a bit of time around noon to refine some things in the presentation. If you can - *please* read it, send me your opinions (may be privately if you want), corrections, ... If you do that later - send them too, but I don't know whether I'll be able to do any changes to it before it's aired. It's available at: http://gadek.debian.net/FOSDEM (apparently xpdf doesn't handle transparent pngs, use OO.o if possible) I'll be back next thursday. Until then I might or might not be able to help with anything about the 1.1.0. At least Chris and David - my kind request - please take care of this and try to finalize it. What remains to be done is: tags, make distchecks, compilation/test from resulting tar.gzs, putting them up somewhere and announcing (www.sablevm.org too). Murphy's law. Oops is down. Maybe oopses or something. It's the worst timing it could ever had. Looks like hardware problem. I won't be able to even take a look at it tomorrow, or move stuff to glue. It means that devel.sablevm.org is down until fixed, probably in a week :-(( Cheers, 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 |
|
From: Heinrich M. <ma...@he...> - 2004-02-18 15:02:55
|
Hi Etienne, hi Grzegorz!
First of all: Thanks for your input!
"Grzegorz B. Prokopski" <ga...@de...> writes:
> W li¶cie z ¶ro, 11-02-2004, godz. 01:55, Etienne Gagnon pisze:
>> Heinrich Moser wrote:
>> > * What version should I use?
>> Currently: The "staging" version. It's the best one available for the moment.
>> Soon, Greg (Grzegorz) and David will release a "bugfree" version which would
>> also be an interesting candidate.
>
> Surely not 1.0.9. I'd say that if you want to develop things - "staging"
> is most likely to be good choice, especially, if you want to be able to
> often feed your improvements back into "staging". [*] But you might
> want to start from some better recognizable point, like ex. the
> soon-to-be-released 1.1.0.
OK, then I'll do some preliminary work and testing with 1.0.9 and then
grab 1.1.0 as soon as it's available.
>> Ideally, whichever version you pick, you should be working within a
>> Subversion working copy, so that you can easily extract "patches" against
>> a "precise" version, e.g.
> Definitely. It will save you lots of time.
I'll do that.
>>> * Did someone already try some benchmarks on SableVM?
>> Look in my Ph.D. thesis for some performance numbers. Others (Greg, David, Chris...)
>> might have additional information. (BTF, AshesX, ... ???)
> See latest mails from Chris, with some results. I also had some, but they'll
> have to be repeated.
Thanks. I've also tried some Java Grande myself in the meantime and
compared them to Chris' output.
> Welcome, and wish you happy hacking!
Thanks. :-) I'll keep you informed about any interesting insights.
SG,
Heinzi
|
|
From: Etienne G. <gag...@uq...> - 2004-02-18 14:56:28
|
Chris Pickett wrote: > (Etienne pls. correct any mistakes ...) Just a clarification: the algorithm was designed to be able to handle situations where the lock owner has changed; the bug was that it didn't handle correctly the case where there was no owner to begin with. > However, I now have another test case (see attached), although I've only > seen this bug manifest itself on a multiprocessor. It might affect > uniprocessors in more complex scenarios. Multi-processor: part of the critical sablevm code for locking does NOT take into account "cache issues". For instance, "xxx.flag" is read and written assuming that any change is visible to other threads without synchronization, which is probably NOT the case on a multiprocessor. So, unless you can actually get your "bug" to manifest itself on a uniprocessor, I wouldn't worry much about it. Now, if you really want to get things running on a multi-processor, you should start investigating cache issues. :-) [WARNING: Not easy. In fact, the Java Memory Model is bronken on multi-processors...] Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ |
|
From: Chris P. <chr...@ma...> - 2004-02-18 06:25:23
|
Etienne Gagnon wrote:
> Etienne Gagnon wrote:
>
>>> It fails in _svmf_enter_object_monitor(). I think Etienne needs to
>>> look at it because he wrote the locking stuff ... I would like to
>>> participate in debugging it but I don't know where to begin. Should
>>> we try, for example, removing thin locks altogether and see if that
>>> fixes it? Or try making some critical sections bigger?
>
>
> OK. The bug has been fixed in staging. Thanks a lot, Chris, for
> providing me (privately) with a small test case, and reporting the
> bug in the first place! :-)
No problem :) Thanks for the fix. In case anyone is wondering, it
was because in trying to acquire a lock, we initially read a lockword as
having no owner. Then, a thinlock was acquired by another thread, and
we had to inflate it, but by now the initial lockword value was stale
and we were getting a NULL pointer to pass to pthread_mutex_lock() when
using the lockword to look up the owner. The solution was simply to
retry locking if the owner is NULL.
(Etienne pls. correct any mistakes ...)
However, I now have another test case (see attached), although I've only
seen this bug manifest itself on a multiprocessor. It might affect
uniprocessors in more complex scenarios.
I get the following about 5% of the time:
Exception in thread "Thread-1" java.lang.NullPointerException
at IncrementRunnable.run (ThreadStarter.java:29)
at java.lang.Thread.run (Thread.java:670)
at java.lang.VMThread.callRun (VMThread.java:116)
at java.lang.Thread.callRun (Thread.java:343)
at java.lang.VirtualMachine.runThread (VirtualMachine.java:117)
I have an instruction trace (it took 26 tries to get it!). All that I
can see is that the NullPointerException appears to be thrown right
after the main() method has exited ... anyway, I'll do some more
digging.
Cheers,
Chris
============ relevant instruction trace =======================
[verbose instructions: executing @0x41353ec4 ALOAD_0]
[verbose instructions: executing @0x41353ec8 DUP]
[verbose instructions: executing @0x41353ecc GETFIELD_INT]
[verbose instructions: executing @0x41353ed8 ICONST_1]
[verbose instructions: executing @0x41353edc IADD]
[verbose instructions: executing @0x41353ee0 PUTFIELD_INT]
[verbose instructions: executing @0x41353eec IINC]
[verbose instructions: executing @0x41353ef8 ILOAD_1]
[verbose instructions: executing @0x41353efc LDC_INTEGER]
[verbose instructions: executing @0x41353f04 IF_ICMPLT_CHECK]
[verbose instructions: executing @0x41353f10 RETURN]
[verbose methods: exiting method IncrementRunnable.run()V]
[ returning to ThreadStarter.main([Ljava/lang/String;)V]
[verbose instructions: executing @0x41353844 REPLACE]
[verbose instructions: executing @0x41353850 GOTO]
[verbose instructions: executing @0x41353734 RETURN]
[verbose methods: exiting method ThreadStarter.main([Ljava/lang/String;)V]
[ returning to
java/lang/VirtualMachine.invokeMain(Ljava/lang/Class;[Ljava/lang/String;)V]
[verbose instructions: executing @0x8050eb0 INTERNAL_CALL_END]
[verbose methods: exiting method
java/lang/VirtualMachine.invokeMain(Ljava/lang/Class;[Ljava/lang/String;)V]
[ returning to
java/lang/VirtualMachine.main([Ljava/lang/String;)V]
[verbose instructions: executing @0x412efff4 REPLACE]
[verbose instructions: executing @0x412f0000 GOTO]
[verbose instructions: executing @0x412eff50 RETURN]
[verbose methods: exiting method
java/lang/VirtualMachine.main([Ljava/lang/String;)V]
[verbose instructions: executing @0x8050eb0 INTERNAL_CALL_END]
[verbose methods: entering method
java/lang/NullPointerException.<init>(Ljava/lang/String;)V]
[verbose instructions: executing @0x41274204 ALOAD_0]
[verbose instructions: executing @0x41274208 ALOAD_1]
[verbose instructions: executing @0x4127420c INVOKESPECIAL]
[verbose methods: entering method
java/lang/RuntimeException.<init>(Ljava/lang/String;)V]
[verbose instructions: executing @0x41273df4 ALOAD_0]
[verbose instructions: executing @0x41273df8 ALOAD_1]
[verbose instructions: executing @0x41273dfc INVOKESPECIAL]
[verbose methods: entering method
java/lang/Exception.<init>(Ljava/lang/String;)V]
[verbose instructions: executing @0x41273e38 ALOAD_0]
[verbose instructions: executing @0x41273e3c ALOAD_1]
[verbose instructions: executing @0x41273e40 INVOKESPECIAL]
[verbose methods: entering method
java/lang/Throwable.<init>(Ljava/lang/String;)V]
[verbose instructions: executing @0x41273e7c ALOAD_0]
[verbose instructions: executing @0x41273e80 INVOKESPECIAL]
[verbose methods: entering method java/lang/Object.<init>()V]
[verbose instructions: executing @0x41251644 RETURN]
[verbose methods: exiting method java/lang/Object.<init>()V]
[ returning to
java/lang/Throwable.<init>(Ljava/lang/String;)V]
[verbose instructions: executing @0x41273e94 ALOAD_0]
[verbose instructions: executing @0x41273e98 ALOAD_0]
[verbose instructions: executing @0x41273e9c PUTFIELD_REFERENCE]
===============================================================
|
|
From: Etienne G. <gag...@uq...> - 2004-02-17 21:26:18
|
Grzegorz B. Prokopski wrote: > (LGPL was _your_ > requirement - how about putting your thesis there then?). A URL to my thesis should be good enough... ;-P Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ |
|
From: Etienne G. <gag...@uq...> - 2004-02-17 21:17:50
|
Etienne Gagnon wrote: >> It fails in _svmf_enter_object_monitor(). I think Etienne needs to >> look at it because he wrote the locking stuff ... I would like to >> participate in debugging it but I don't know where to begin. Should >> we try, for example, removing thin locks altogether and see if that >> fixes it? Or try making some critical sections bigger? OK. The bug has been fixed in staging. Thanks a lot, Chris, for providing me (privately) with a small test case, and reporting the bug in the first place! :-) Have fun! Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-17 19:50:26
|
On Tue, 2004-02-17 at 12:53, Etienne Gagnon wrote: > Grzegorz B. Prokopski wrote: > > I have the presentation I did at Sable meeting in .pdf format, I also > > have Etienne's Cascon presentation. I can say mine is LGPLed, I guess > > Etienne can say the same about his. > > OK for the presentation. Good. > > Do you have some other presentations (or other docs) that you think > > might and should be put there? I for ex. thought about David's > > presentation(s) about SableJIT and if there's no reason to hold > > them unpublished (I can image some such reasons) - I'd like to > > ask for them - preferably .pdf (or .ps) and under LGPL. You can > > send me a private email w/ them. > > > > I would also like to put a copy of Etienne's PhD thesis there (are > > they LGPLed btw? ;-) > > My thesis is not licensed under the LGPL. It has no explicit license, > only the implicit "you may download it and read it" license (being > available online). > > I do not think that it is appropriate to license research papers under > the LGPL. It would be OK to do so, if we wrote a "user manual". This > is probably already the case with the "man page". > > There is a svn+ssh://svn.sablevm.org/group/ repository (available to people > that have to add "/public/" to access the public repository) that is more > appropriate for sharing group-specific documents. I can also provide > "private" repositories, accessible to one person and myself only, ideal > for working on new papers & theses. OK, I understand. But the reason why I asked for that is to gather some documentation in (pretty much empty) ./docs directory. I (personaly) don't care about the docs source codes ATM, I don't care about the exact license as long as it permits distribution. (LGPL was _your_ requirement - how about putting your thesis there then?). I'd love to put David's presentation there too, but the one that is available on his home site is quite preliminary/outdated. OTOH, as I said originally, I understand that there can be perfectly good reasons for not publishing these things (yet). Cheers, GBP |
|
From: Etienne G. <gag...@uq...> - 2004-02-17 18:07:31
|
Grzegorz B. Prokopski wrote: > I have the presentation I did at Sable meeting in .pdf format, I also > have Etienne's Cascon presentation. I can say mine is LGPLed, I guess > Etienne can say the same about his. OK for the presentation. > Do you have some other presentations (or other docs) that you think > might and should be put there? I for ex. thought about David's > presentation(s) about SableJIT and if there's no reason to hold > them unpublished (I can image some such reasons) - I'd like to > ask for them - preferably .pdf (or .ps) and under LGPL. You can > send me a private email w/ them. > > I would also like to put a copy of Etienne's PhD thesis there (are > they LGPLed btw? ;-) My thesis is not licensed under the LGPL. It has no explicit license, only the implicit "you may download it and read it" license (being available online). I do not think that it is appropriate to license research papers under the LGPL. It would be OK to do so, if we wrote a "user manual". This is probably already the case with the "man page". There is a svn+ssh://svn.sablevm.org/group/ repository (available to people that have to add "/public/" to access the public repository) that is more appropriate for sharing group-specific documents. I can also provide "private" repositories, accessible to one person and myself only, ideal for working on new papers & theses. Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ |
|
From: Etienne G. <gag...@uq...> - 2004-02-17 17:18:55
|
Hi Andreas,
It's a problem with your class file, not a problem with SableVM.
Using Sun's JDK:
$ java -verify BFprogram
Exception in thread "main" java.lang.ClassFormatError: BFprogram (Extra bytes at the end of the class file)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:537)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
ooO( lucky me! ) ;-)
Etienne
PS: SableVM has no verifier, yet it does actually enforce some basic
stuctural integrity rules on class files.
Andreas Heck wrote:
> Hello everybody,
>
> I have run into a execution problem with SableVM. When I start the
> program which is appended to this mail on LinuxPPC with SableVM I get
> the following error message:
>
> java.lang.ClassFormatError
>
> When I execute it with kaffe on the same machine or with Sun's jre 1.4.2 on
> Win2K it runs without any problems.
>
> The program is written in jasmin assembly code. Don't wonder about the
> weird code. It's the output of a brainfuck compiler I'm playing around
> with at the moment.
>
>
> Andreas
>
--
Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/
SableVM: http://www.sablevm.org/
SableCC: http://www.sablecc.org/
|
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-17 07:47:22
|
W li=B6cie z wto, 17-02-2004, godz. 01:47, Randolph Chung pisze:=20 > > What is the status of libffi on hppa? I was told by Tom Tromey that > > GCC's upstream was not affected by the breakin into FSF's servers > > as the project is hosted elsewhere. And Debian infrastructure is also > > back and in shape. >=20 > Sorry it took so long; been very busy with various things. >=20 > Anyway, Debian unstable now has a backported version of libffi (many > thanks to doko for picking that up so quickly). Next step is to submit=20 > patches against cvs to upstream. I may be without internet connection=20 > for a few days though, but i'll try to get that out ASAP. Sounds great, thanks a lot guys! I guess it'd be good time to re-try SableVM on tausq's machine and/or on paer. My latest experiences w/ paer were completly different from what we observed on tausq's machine. On paer it just didn't work :-( I'll be away for a week (FOSDEM + a few days) but I'd be thankful if you were so nice to try it and sent an email how it went. Latest staging and hopefuly soon-to-be-released 1.1.0 contain hppa port pieces. Cheers! Grzegorz B. Prokopski --=20 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 |
|
From: Chris P. <chr...@ma...> - 2004-02-17 01:06:33
|
Grzegorz B. Prokopski wrote: > Hi all, > > I think it wouldn't be bad idea to put the presentation slides about > SableVM into devel.s.o/docs/ directory. what is "devel.s.o"? I discussed it w/ Etienne > the other day and the only requirement he had for these docs was > that they were under LGPL (or more permessive license). > > I have the presentation I did at Sable meeting in .pdf format, I also > have Etienne's Cascon presentation. I can say mine is LGPLed, I guess > Etienne can say the same about his. > > Do you have some other presentations (or other docs) that you think > might and should be put there? I for ex. thought about David's > presentation(s) about SableJIT and if there's no reason to hold > them unpublished (I can image some such reasons) - I'd like to > ask for them - preferably .pdf (or .ps) and under LGPL. You can > send me a private email w/ them. I have some presentations and reports, but nothing official. However, I don't want to put them in just yet; I might want to reuse some of the figures or text for submitted work, and depending on the journal / conference / publisher / whatever, that might preclude releasing them under the LGPL (not sure, but Etienne did say this might be a problem). I think putting .ps and .pdf and .png is equivalent to putting binaries in. If they're going to be in there, they should be built from .tex et al. (otherwise, what is the point? It is only going to inflate the size of the code tree). But ... for actual final copies of documents, I think it's better to make a page somewhere called "papers and presentations" and link to it from sablevm.org. I would personally rather see us focus on getting the files we currently have into some kind of .texinfo format or something first, before going on a hunt for even more information. And rather than a collection of papers, I think we need some kind of coherent document describing the structure and function of SableVM from a developer's perspective. Something that a developer can read easily using his or her terminal. So ... I think we should organize what we have into .texinfo, make it nice and installable and browsable, and then convert TeX sources of non-repository papers, presentations, theses, and other publications into either plain text (or perhaps directly into .texinfo?) before putting them into the repository (provided we have permission). Sorry if this was long :( Cheers, Chris |
|
From: Andreas H. <ah...@mo...> - 2004-02-16 13:30:52
|
Hello everybody, I have run into a execution problem with SableVM. When I start the program which is appended to this mail on LinuxPPC with SableVM I get the following error message: java.lang.ClassFormatError When I execute it with kaffe on the same machine or with Sun's jre 1.4.2 on Win2K it runs without any problems. The program is written in jasmin assembly code. Don't wonder about the weird code. It's the output of a brainfuck compiler I'm playing around with at the moment. Andreas -- "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-16 08:09:53
|
Hi all, I think it wouldn't be bad idea to put the presentation slides about SableVM into devel.s.o/docs/ directory. I discussed it w/ Etienne the other day and the only requirement he had for these docs was that they were under LGPL (or more permessive license). I have the presentation I did at Sable meeting in .pdf format, I also have Etienne's Cascon presentation. I can say mine is LGPLed, I guess Etienne can say the same about his. Do you have some other presentations (or other docs) that you think might and should be put there? I for ex. thought about David's presentation(s) about SableJIT and if there's no reason to hold them unpublished (I can image some such reasons) - I'd like to ask for them - preferably .pdf (or .ps) and under LGPL. You can send me a private email w/ them. I would also like to put a copy of Etienne's PhD thesis there (are they LGPLed btw? ;-) I might have missed some other docs that might be worth putting there - ideas are appreciated. Cheers, 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 |
|
From: David <db...@CS...> - 2004-02-16 00:06:19
|
On Sun, Feb 15, 2004 at 09:32:31AM -0500, Etienne Gagnon wrote: >=20 > I'll let David take care of your patch (and see if it can be accepted > according to the FSF's contribution rules). >=20 I applied the patch. 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 |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-15 20:04:51
|
W li=B6cie z nie, 15-02-2004, godz. 09:09, Martin Michlmayr pisze:=20 > * Grzegorz B. Prokopski <ga...@de...> [2004-02-02 04:17]: > > Spoiler: if there the basic libffi functions were available on > > mips/mipsel I could very easily make SableVM Java Virtual Machine > > run on these. > >=20 > > Apparently there are some people upstream that work on libffi for > > mips/mipsel ex. http://gcc.gnu.org/ml/gcc-patches/2003-09/msg01053.ht= ml > >=20 > > SableVM only needs two basic functions: ffi_prep_cif and ffi_call, > > and NOT the whole libffi, with advanced stuff like closures. > >=20 > > Therefore would it be possible to have libffi for mips/mipsel built a= s > > Debian package? >=20 > Note that I'm no mips expert, so I cannot help you fixing stuff, but > I do have a mips/mipsel machine so I can help you test stuff. In any > case, doko said that libffi should become available for mipsel with > GCC 3.4 (see #229844). Once that happens, I'd be happy to test > SableVM on my mips box and perhaps also provide you remote access. Hi Martin! That would be really great! I hope it won't take too long before gcc 3.4 (-0preX) hits unstable (probably as we release sarge, no? ;-) Looking forward to make SableVM work on mips/mipsel Grzegorz B. Prokopski PS: Cc:ing SableVM-devel ML w/ these news. I hope you don't mind. PPS: In fact, if we have everything installed BUT the libffi, then it's quite easy to just fetch gcc-3.4 source and compile libffi only. See http://devel.sablevm.org/wiki/LibFFI for instructions. If you were able to fill in needed info in system.c and system.h files - then I think you can make SableVM work on mips "just like that". Ignore cache flush function, you only need atomic compare&swap (or make a plai-C stuf at first), and basic informations about word/page size of your arch. Hm... I've just written quick porting guide at http://devel.sablevm.org/wiki/Porting --=20 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 |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-15 19:26:55
|
W li=B6cie z nie, 15-02-2004, godz. 13:36, Chris Pickett pisze:=20 > Etienne Gagnon wrote: > > - it should also report about the status of "--disable-no-reorder-blo= ck" > > and all other "configure" options that were explicitly or implicitl= y > > selected. >=20 > Otherwise, I'm not sure what you mean by "report". Where do you want=20 > this reported? $ sablevm -V SableVM version 1.0.9+staging - compile date and time: 2004-02-15 08:09:31 UTC - gcc version: 3.3.2 (Debian) - inlinability testing enabled - signal based exception detection - copying garbage collection - bidirectional object layout - inline-threaded interpreter Currently information about --disable-no-reorder-blocks is missing. GBP --=20 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 |
|
From: Chris P. <chr...@ma...> - 2004-02-15 19:20:36
|
Grzegorz B. Prokopski wrote: > W li=B6cie z nie, 15-02-2004, godz. 12:58, Chris Pickett pisze:=20 >=20 >>Etienne Gagnon wrote: >> >>>Another thing: I do really think that "./configure ; make ; make inst= all" >>>should work out-of-the-box for sablevm-x.y.z.tar.gz and for >>>sablevm-classpath-x.y.z.tar.gz. Currently, it is broken for >>>sablevm-classpath (as you need to pass specific configure options to g= et >>>a sablevm usable build). Assume that the typical user WILL NOT read t= he >>>README file nor the INSTALL files and will simply go ahead and type th= e >>>standard commands above. [Alternatively, you could make sure that >>>"./configure" fails for sablevm-classpath, and issues a message inviti= ng >>>the user to read the README and INSTALL files...] >>> >>>The worst situation is if a user does the standard commands, gets no b= uild >>>error message, yet gets "could not start vm" when trying to run HelloW= orld. >>> >>>What do you think? >> >>I think adjusting classpath's configure.ac to recognize our options as = >>defaults should not be too hard (including --enable-gtk-peer=3Dno as de= fault). >=20 >=20 > No GTK? Why?! IMO this one surely should be "yes" by default. I don't know, I was thinking that a minimal barrier to success was good. = It's just one more dependency to take care of. It's really fine=20 either way. > OTOH I'd love to have some not-too-big AWT app with which I could > test this feature (not gnome-java). Any suggestions? You might find something here: http://www.epcc.ed.ac.uk/javagrande/links.html >>On the other hand, it is also not too hard to include David's=20 >>build_sablevm-classpath script. >=20 >=20 > I think adjusting configure would be better percieved by the users, as > ./configure [ --prefix=3D... ]; make ; make install > is what works for 90% of the free software. okay :) The only reason I made the comment was because I thought it=20 might make it easier to merge classpath updates from upstream. But I=20 agree: ./configure [ --prefix=3D... ]; make ; make install is best for=20 the end user. It also tends to indicate a well-maintained piece of=20 software. Chris |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-15 19:02:55
|
W li=B6cie z nie, 15-02-2004, godz. 13:02, Chris Pickett pisze:=20 > Grzegorz B. Prokopski wrote: > > Anyway - can David or you just finish the release, please? > >=20 > Etienne, is it okay to give Greg write access to sablevm-classpath, and= =20 > just make sure to revert all of his changes before sending patches upst= ream? This particular, ehm... patch (?) will never be submitted upstream anyway. But we should not bend the rules. I have the papers signed already, I just need to get a postage stamp to send it (post office seems to be _always_ closed when I pass by ;-) Hopefuly for 1.1.1 I will have it done already. GBP --=20 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 |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-15 18:50:17
|
W li=B6cie z nie, 15-02-2004, godz. 12:58, Chris Pickett pisze:=20 > Etienne Gagnon wrote: > > Another thing: I do really think that "./configure ; make ; make ins= tall" > > should work out-of-the-box for sablevm-x.y.z.tar.gz and for > > sablevm-classpath-x.y.z.tar.gz. Currently, it is broken for > > sablevm-classpath (as you need to pass specific configure options to = get > > a sablevm usable build). Assume that the typical user WILL NOT read = the > > README file nor the INSTALL files and will simply go ahead and type t= he > > standard commands above. [Alternatively, you could make sure that > > "./configure" fails for sablevm-classpath, and issues a message invit= ing > > the user to read the README and INSTALL files...] > >=20 > > The worst situation is if a user does the standard commands, gets no = build > > error message, yet gets "could not start vm" when trying to run Hello= World. > >=20 > > What do you think? >=20 > I think adjusting classpath's configure.ac to recognize our options as=20 > defaults should not be too hard (including --enable-gtk-peer=3Dno as de= fault). No GTK? Why?! IMO this one surely should be "yes" by default. OTOH I'd love to have some not-too-big AWT app with which I could test this feature (not gnome-java). Any suggestions? > On the other hand, it is also not too hard to include David's=20 > build_sablevm-classpath script. I think adjusting configure would be better percieved by the users, as ./configure [ --prefix=3D... ]; make ; make install is what works for 90% of the free software. GBP --=20 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 |
|
From: Chris P. <chr...@ma...> - 2004-02-15 18:38:02
|
Etienne Gagnon wrote: > Chris Pickett wrote: > >>> But I am sure staging shouldn't claim to be just "1.0.9" or any other >>> release. I wanted to put "staging" name initialy, but I guess >>> "1.0.9+staging" or (hopefuly soon) "1.1.0+staging" should at least give >>> some more informations if we ask a user to do 'sablevm -V' for us. >> > I think that sablevm staging should report: > - SableVM version "Staging Sapshot" (optionally with a UTC date/time... > but that would be a hassle as what we want is the svn revision checkin > UTC date/time, not the "build or configure" date/time). Be warned: > svn log reports "local" date/time. I don't think time is as meaningful as just revision number. $ svn info | grep "Last Changed Rev:" | cut -d' ' -f4 is a useful pipeline :) However, what's the best place to do the find and replace? In configure.ac? That way I think the number would make it into a tarball. > - it should also report about the status of "--disable-no-reorder-block" > and all other "configure" options that were explicitly or implicitly > selected. What if the binary / directory names simply reflect all non-default configure options, aside from the switch/direct/inlined choice? (so, sablevm-staging-rXXXX-inlined is the default) Otherwise, I'm not sure what you mean by "report". Where do you want this reported? $ cat config.log | grep '^#define _SABLEVM' seems pretty good -- I currently get the following: #define _SABLEVM_BIDIRECTIONAL_OBJECT_LAYOUT 1 #define _SABLEVM_COPY_GC 1 #define _SABLEVM_PACKAGE_NAME "sablevm" #define _SABLEVM_PACKAGE_VERSION "1.0.9" <-- becomes "staging-rXXXX" #define _SABLEVM_SWITCH_THREADED_INTERPRETER 1 Cheers, Chris |
|
From: Chris P. <chr...@ma...> - 2004-02-15 18:03:47
|
Grzegorz B. Prokopski wrote: > W li=B6cie z nie, 15-02-2004, godz. 09:32, Etienne Gagnon pisze:=20 >=20 >>Hi Greg, >> >>Only developers that have done the FSF paperwork thing (e.g. copyright >>assignment) have write access to sablevm-classpath. So, both David >>and I have access to it for the time being. >=20 > Heh, I *do* know that. >=20 >=20 >>I'll let David take care of your patch (and see if it can be accepted >>according to the FSF's contribution rules). >=20 > Ehm... You haven't even spent 0.5sec looking at it, right? > It's a half liner, that changes only sablevm-specific thing, > that is sets AC_INIT to this: >=20 > AC_INIT([SableVM GNU Classpath > 0.07+cvs],[1.0.9+staging],[cla...@gn...],[sablevm-classpath]) >=20 > Anyway - can David or you just finish the release, please? >=20 Etienne, is it okay to give Greg write access to sablevm-classpath, and=20 just make sure to revert all of his changes before sending patches upstre= am? Chris |
|
From: Chris P. <chr...@ma...> - 2004-02-15 18:00:28
|
Etienne Gagnon wrote: > Chris Pickett wrote: > >>> 2. Updated http://devel.sablevm.org/docs/INSTALL.txt document, which >>> serves as both: release notes and installation instruction, and put it >>> into sablevm/staging as INSTALL-DEVEL text file (made it included in >>> the "dist" tarball - should be removed on migration to trunk!). >> >> >> >> Seems like common practice would be to put a single INSTALL file in >> the top level of sablevm. > > > I agree with the INSTALL file. > > Another thing: I do really think that "./configure ; make ; make install" > should work out-of-the-box for sablevm-x.y.z.tar.gz and for > sablevm-classpath-x.y.z.tar.gz. Currently, it is broken for > sablevm-classpath (as you need to pass specific configure options to get > a sablevm usable build). Assume that the typical user WILL NOT read the > README file nor the INSTALL files and will simply go ahead and type the > standard commands above. [Alternatively, you could make sure that > "./configure" fails for sablevm-classpath, and issues a message inviting > the user to read the README and INSTALL files...] > > The worst situation is if a user does the standard commands, gets no build > error message, yet gets "could not start vm" when trying to run HelloWorld. > > What do you think? I think adjusting classpath's configure.ac to recognize our options as defaults should not be too hard (including --enable-gtk-peer=no as default). On the other hand, it is also not too hard to include David's build_sablevm-classpath script. Cheers, Chris |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-15 17:58:34
|
W li=B6cie z nie, 15-02-2004, godz. 09:41, Etienne Gagnon pisze:=20 > Chris Pickett wrote: > >> 2. Updated http://devel.sablevm.org/docs/INSTALL.txt document, which > >> serves as both: release notes and installation instruction, and put = it > >> into sablevm/staging as INSTALL-DEVEL text file (made it included in > >> the "dist" tarball - should be removed on migration to trunk!). > >=20 > >=20 > > Seems like common practice would be to put a single INSTALL file in t= he=20 > > top level of sablevm. >=20 > I agree with the INSTALL file. Well, I could simply rip-off the upper part of the file, which says things about "build" and "build-many" scripts, downloading 3 tarballs, etc. In general all that seems rather outdated. The question is whether we want to keep any of this stuff? There's no build script in staging's sablevm. If you don't mind - then I'll go and put current build instructions there instead. And split news into NEWS. This should probably be done before tagging 1.1.0 in bugfree. > Another thing: I do really think that "./configure ; make ; make insta= ll" > should work out-of-the-box for sablevm-x.y.z.tar.gz and for > sablevm-classpath-x.y.z.tar.gz. Currently, it is broken for > sablevm-classpath (as you need to pass specific configure options to ge= t > a sablevm usable build). Assume that the typical user WILL NOT read th= e > README file nor the INSTALL files and will simply go ahead and type the > standard commands above. [Alternatively, you could make sure that > "./configure" fails for sablevm-classpath, and issues a message invitin= g > the user to read the README and INSTALL files...] I agree. Any takers? That should be just some playing w/ configure's defaults, so that --prefix was enough to set --libdir and --datadir properly to sablevm's needs. (though I don't see it as 1.1.0 showstopper). > The worst situation is if a user does the standard commands, gets no bu= ild > error message, yet gets "could not start vm" when trying to run HelloWo= rld. >=20 > What do you think? This will be our first (and most used) FAQ entry. *g* (and there's more than one answer to that too) Cheers, Grzegorz B. Prokopski --=20 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 |
|
From: Grzegorz B. P. <ga...@de...> - 2004-02-15 17:24:58
|
W li=B6cie z nie, 15-02-2004, godz. 09:32, Etienne Gagnon pisze:=20 > Hi Greg, >=20 > Only developers that have done the FSF paperwork thing (e.g. copyright > assignment) have write access to sablevm-classpath. So, both David > and I have access to it for the time being. Heh, I *do* know that. > I'll let David take care of your patch (and see if it can be accepted > according to the FSF's contribution rules). Ehm... You haven't even spent 0.5sec looking at it, right? It's a half liner, that changes only sablevm-specific thing, that is sets AC_INIT to this: AC_INIT([SableVM GNU Classpath 0.07+cvs],[1.0.9+staging],[cla...@gn...],[sablevm-classpath]) Anyway - can David or you just finish the release, please? GBP --=20 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 |
|
From: Etienne G. <gag...@uq...> - 2004-02-15 15:15:10
|
Chris Pickett wrote: >> But I am sure staging shouldn't claim to be just "1.0.9" or any other >> release. I wanted to put "staging" name initialy, but I guess >> "1.0.9+staging" or (hopefuly soon) "1.1.0+staging" should at least give >> some more informations if we ask a user to do 'sablevm -V' for us. > I think that sablevm staging should report: - SableVM version "Staging Sapshot" (optionally with a UTC date/time... but that would be a hassle as what we want is the svn revision checkin UTC date/time, not the "build or configure" date/time). Be warned: svn log reports "local" date/time. - it should also report about the status of "--disable-no-reorder-block" and all other "configure" options that were explicitly or implicitly selected. Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ |
6 messages has been excluded from this view by a project administrator.
