Hi,
On Sun 26 Jul 2009 14:01, Andy Wingo writes:
> On Fri 17 Jul 2009 19:27, Martin Ward writes:
>
>> Testing prog_to_spec_TEST.scx:
>>
>> Guile 1.9.1: 260.9 secs
>> Guile 1.8.7: 135.9 secs
>> Gambit v4.4.4:88.3 secs
>> SCM version 5e5: 29.4 secs
>> Hobbit compiled: 1.3 secs
>
>
Hi Martin,
On Fri 17 Jul 2009 19:27, Martin Ward writes:
> Now here's something totally wierd with Guile 1.8.7:
>
> echo '(load "ALL.scm")(load "prog_to_spec_TEST.scx")(exit)' | /usr/bin/time
> guile
>
> takes 139 seconds CPU time.
>
> /usr/bin/time guile -l ALL.scm -s prog_to_spec_TEST.scx
>
>
On Mon 20 Jul 2009 14:48, Martin Ward writes:
> On Sunday 19 Jul 2009 23:03, Andy Wingo wrote:
>> Discussed here:
>>
>> http://article.gmane.org/gmane.lisp.guile.devel/8882
>>
>> I'm working on a fix, hopefully within a couple of days.
>
> Great! Let me know when it is ready, and I'll put it th
Andy Wingo writes:
[...]
> Discussed here:
>
> http://article.gmane.org/gmane.lisp.guile.devel/8882
Oops, sorry for repeating what you had already said.
Thanks,
Ludo'.
On Sunday 19 Jul 2009 23:03, Andy Wingo wrote:
> Discussed here:
>
> http://article.gmane.org/gmane.lisp.guile.devel/8882
>
> I'm working on a fix, hopefully within a couple of days.
Great! Let me know when it is ready, and I'll put it through
its paces for you.
> > Its a pity that you decided
Hello,
On Sun 19 Jul 2009 15:56, Martin Ward writes:
> On Friday 17 Jul 2009 19:10, Ludovic Courtès wrote:
>> You can work around it by manually compiling your source files:
>>
>> guile-tools compile -o ALL.go ALL.scm
>> ...
>>
>> The compiled version can then be run with something like:
>>
On Friday 17 Jul 2009 19:10, Ludovic Courtès wrote:
> You can work around it by manually compiling your source files:
>
> guile-tools compile -o ALL.go ALL.scm
> ...
>
> The compiled version can then be run with something like:
>
> guile -c '(load-compiled "ALL.go")'
>
> Can you try this?
Th
Hi,
Martin Ward writes:
> Now here's something totally wierd with Guile 1.8.7:
>
> echo '(load "ALL.scm")(load "prog_to_spec_TEST.scx")(exit)' | /usr/bin/time
> guile
>
> takes 139 seconds CPU time.
>
> /usr/bin/time guile -l ALL.scm -s prog_to_spec_TEST.scx
>
> takes only 56 seconds CPU time.
Now here's something totally wierd with Guile 1.8.7:
echo '(load "ALL.scm")(load "prog_to_spec_TEST.scx")(exit)' | /usr/bin/time
guile
takes 139 seconds CPU time.
/usr/bin/time guile -l ALL.scm -s prog_to_spec_TEST.scx
takes only 56 seconds CPU time.
You read that right: if I pass the files
Hi,
Martin Ward writes:
> The only file in ~/.cache is guile-1.9.1/test-suite/lib.scm.go
Then there must be something wrong.
If you unset GUILE_AUTO_COMPILE, Guile should automatically compile all
source files not already compiled and store them under ~/.cache. When
it does, it prints lines t
On Thursday 16 Jul 2009 08:59, Neil Jerram wrote:
> Martin Ward writes:
> > Running a test program on Guile 1.8.7 takes 100 seconds CPU time.
> > On Guile 1.9.0 (beta) the same program takes 237 seconds CPU time!
>
> I wonder if that's because the code is being auto-compiled? Do you
> get a bette
Neil Jerram writes:
> Martin Ward writes:
>
>> Running a test program on Guile 1.8.7 takes 100 seconds CPU time.
>> On Guile 1.9.0 (beta) the same program takes 237 seconds CPU time!
>
> I wonder if that's because the code is being auto-compiled? Do you
> get a better result if you set environm
Martin Ward writes:
> Running a test program on Guile 1.8.7 takes 100 seconds CPU time.
> On Guile 1.9.0 (beta) the same program takes 237 seconds CPU time!
I wonder if that's because the code is being auto-compiled? Do you
get a better result if you set environment variable GUILE_AUTO_COMPILE
Running a test program on Guile 1.8.7 takes 100 seconds CPU time.
On Guile 1.9.0 (beta) the same program takes 237 seconds CPU time!
For comparison:
Gambit v4.4.4 takes 60 seconds.
SCM version 5e5 takes 20.7 seconds.
Hobbit compiled code running under SCM takes 1.1 seconds!
There was some talk
14 matches
Mail list logo
