Linas Vepstas linasveps...@gmail.com writes:
I reviewed patch2 as best I could,
Thanks!
it looks to me like new_bucket is never released.
I assume that the scm_acons did a malloc, but
maybe not
Yes, but the garbage collection will find and free it, so it's OK.
Regards,
Neil
Hi Neil,
Neil Jerram n...@ossau.uklinux.net writes:
I'm not sure about moving stack-limit-calibration.scm from TESTS to
BUILT_SOURCES. The point of putting it in TESTS was to help with
cross-compiling. When cross-compiling, my understanding is that
`make' should be run in a build host
Hi Neil,
Neil Jerram n...@ossau.uklinux.net writes:
That's an interesting idea, but to be honest I'd prefer to finish this
work and move onto something else. Would it be OK just to reduce the
default runtime to 2 seconds? (It wouldn't make any practical
difference, because 10 seconds isn't
Albert Chin guile-de...@mlists.thewrittenword.com writes:
libguile/__scm.h has:
# if defined (__ia64__)
/* For IA64, emulate the setjmp API using getcontext. */
# include signal.h
# include ucontext.h
typedef struct {
ucontext_t ctx;
int fresh;
} jmp_buf;
#
2009/3/26 Neil Jerram n...@ossau.uklinux.net:
- and that scm_c_eval_string consists of reading (= symbol lookup)
followed by evaluation (= module obarray lookup), and that each
scm_c_eval_string call is fast enough to be completed well within one
time slice.
One way to stress test such
