Hi!
Juhani Viheräkoski writes:
> With recent changes in guile vm there are lots on improvements on the
> Gambit benchmarks.
Improvements compared to what?
> In the worst case some test run 10% slower
Slower than what?
> but there are huge wins in testcases involving vectors offsetting
> thi
Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>> Maybe 1.8.7 is approaching now?
>
> Yes, that would be good. It might just be worth fixing the jmp_buf
> definition problem before that (which I should get to in the next week
> or so) - but on the other hand we already have plenty
Hello,
Neil Jerram writes:
> Firstly, now that 1.9.0 has been released, I'm not sure it makes sense
> for 1.9.x NEWS to refer to `Changes in 1.8.x' for x >= 7.
IMO, when 2.0 is released, we really want to show changes since the
1.8.x series, i.e., essentially broad changes, rather than changes
l...@gnu.org (Ludovic Courtès) writes:
> There's no `(ice-9 i18n)' in 1.8.
> The patch at [1] shouldn't be needed because the Libtool-generated
> `libguile/guile' scripts does the right thing wrt. the libraries the
> executable is linked against (i.e., libguile, libgmp, etc.).
Sorry, I see now a
l...@gnu.org (Ludovic Courtès) writes:
> Cool, thanks for going over all these loose ends! ;-)
I'm really happy to be getting through them... these are things that
have been sitting in my inbox for ages.
> Maybe 1.8.7 is approaching now?
Yes, that would be good. It might just be worth fixing
Daniel Kraft writes:
> it seems so. Doing just a
>
> scheme@(guile-user)> (if %nil 1 2)
> 1
>
> with a recent build (of at least my elisp branch, but that did not
> change anything in this respect of course) gives that answer.
>
> Doing ,o interp #t as Andy did however also gives the right answe
Neil Jerram writes:
> Below is a patch for review. It was an interesting problem, as I
> haven't gone very far into Guile's number handling code before.
I've pushed this to master too, and that raises two points about the
organization of master's NEWS.
Firstly, now that 1.9.0 has been released
Hello,
here there are the results of what I've discovered on compiling the very latest
sources of guile under mingw+msys.
I sent a message into mingw-user mailing list and I discovered that I had one
of the components of msys not up to date.
It seems you need msyscore to be at least 1.0.10 or new
The new vector vm code gives me quite a few "possible use uninitialized"
warnings.
On debian Etch:
$ gcc --version
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
Patch attached (I hope).
-Dale
init-vars.patch
Description: Binary data
Hi,
With recent changes in guile vm there are lots on improvements on
the Gambit benchmarks. In the worst case some test run 10% slower but there
are huge wins in testcases involving vectors offsetting this. Here are
*some* of the highlights:
triangl:
-15.57user 0.04system 0:15.72elapsed 99%C
Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Not quite. If get/release are left as is (i.e., they do not establish a
>> dynwind context), I would write something along the lines of:
>>
>> You must take care to always unreserve an array after reserving it,
>> also in t
Hello,
Neil Jerram writes:
> Andy Wingo writes:
>
>> On Fri 22 Aug 2008 11:56, l...@gnu.org (Ludovic Courtès) writes:
>>
>>> Just to make sure, I also ran `pre-inst-guile', typed
>>> "(use-modules (ice-9 i18n))" and attached GDB to it: it shows that the
>>> right `libguile-i18n' is loaded.
>>
>
12 matches
Mail list logo
