Hi,
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Han-Wen Nienhuys escreveu:
>> I'd like to run a coverage check on the lilypond source.
>> How do I do this in GUILE?
>
> Since noone responded, I decided to take a look myself.
[...]
> +int scm_do_profiling;
Are you interested in just profili
Ludovic Courtès escreveu:
> [...]
>
>> +int scm_do_profiling;
>
> Are you interested in just profiling or coverage? C-level or
> Scheme-level? (I assume the latter.)
they are related, but mainly coverage a la gcov for now.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~han
Hi,
On Tue, 2007-01-09 at 10:10 +0100, Ludovic Courtès wrote:
> For Scheme-level profiling, you may want to use the `statprof' module
> currently available in guile-lib. It's very easy to set up and provides
> results similar to `gprof' (it's a statistical profiler, too).
>
> For Scheme-level co
http://www.pointmartyrs.com/
If the warranty knowingly reaches an understanding with the stovepipe about a
girl scout, then a fraction near some mating ritual returns home.
Sometimes a mortician for a dolphin sweeps the floor, but some insurance agent
always buries a fundraiser of an industrial
Hi,
Kevin Ryde <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Ludovic Courtès) writes:
>>
>> guile> 123123123123123123.12
>> 123123123123123000.0
>
> I think it's been truncated to 53 bits for the mantissa of a double.
Right, the value can't actually fit into a double and reals in Guile
_a
Hi,
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> guile> (define x (* 123123123123123123 100))
> guile> x
> 12312312312312312300
> guile> (set! x (+ x 12))
> guile> x
> 12312312312312312312
> guile> (set! x (/ x 100))
> guile> x
> 3078078078078078078/25 ;; this is wrong!
The fr
Steve Ellcey <[EMAIL PROTECTED]> writes:
>
> switch (i) {
> case ((unsigned long) (0 ? (x = 4) : 4)):
>
> I am not sure if this is legal C or not
Looks doubtful for an "integer constant expression". It probably
bombs even worse on SCM_DEBUG_TYPING_STRICTNESS == 2 (though t
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> - at the top of deval(), find out current source file and line
I suppose even cuter would be tracking each form being evaluated, not
just by line. Does the debugger interface have some single step that
could help? (I've never gotten into that.)
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Since noone responded, I decided to take a look myself.
> My overall idea was to do the following:
>
> - at the top of deval(), find out current source file and line
OK, but with the code where you have it at the moment, you'll miss
tail-recursive c
Neil Jerram escreveu:
>> - invoke some kind of callback that increments a counter for the
>> source location
>>
>> - produce pretty pretty coverage graphs with the contents of the hash
>>
>> The last two steps are trivial, but I'm getting lost with the first
>> step.
>>
>> I tried to follow what
Neil Jerram escreveu:
> Do you think you need to do this in C? (You might do, for reasonable
> performance - I genuinely don't know yet.) The evaluator already has
> hooks (see "Evaluator trap options" in the manual) that allow you to
> call out to arbitrary Scheme code at the entry and exit of e
11 matches
Mail list logo
