* Peter Bex peter@xs4all.nl [130525 17:16]:
On Sat, May 25, 2013 at 05:05:57PM +0200, Kristian Lein-Mathisen wrote:
Dear Chickeners,
With the help of C-Keen, I've been able to make small patch that prevents a
segfault. The patch is attached.
Looks good! Thanks a bunch. I've
* Evan Hanson ev...@foldling.org [130527 09:20]:
On 2013/05/26 09:41P, Evan Hanson wrote:
The attached patch adds support and basic tests for case clauses
containing `=` patterns (R7RS 4.2.1).
I just noticed the two comments in this patch are inverted; please find
attached a hand-munged
Hi Peter.
Wed, 29 May 2013 19:06:26 +0200, Peter.Bex wrote:
This patch should fix it, but it does in a roundabout way: converting
the number to a string causes it to lose precision because of the default
value of (flonum-print-precision). It's more explicit to check whether
the two values
I am curious why this happens though. The only thing I could think of was the
number is being constant folded in one case or being computed in one case via a
hardware intrinsic instead of libm in the other, but the generated C code looks
identical in both cases. Perhaps some previous register
On Wed, May 29, 2013 at 10:03:09PM +0200, Christian Kellermann wrote:
* Evan Hanson ev...@foldling.org [130527 09:20]:
I just noticed the two comments in this patch are inverted; please find
attached a hand-munged version with this fixed, and sorry for the noise.
Thanks, this one looks
On May 29, 2013, at 3:53 PM, Peter Bex peter@xs4all.nl wrote:
The fpsin expands to a C inline call to sin(), whereas the sin() call
expands to a call to C_a_i_flonum_sin, which is not inlineable so it has
to issue a proper function call. This then goes through libm, which is
potentially
