[m-rev.] for review: coverage testing
Julien Fischer
juliensf at csse.unimelb.edu.au
Wed Sep 20 15:13:08 AEST 2006
On Wed, 20 Sep 2006, Zoltan Somogyi wrote:
> On 20-Sep-2006, Zoltan Somogyi <zs at csse.unimelb.edu.au> wrote:
>> so I have actually
>> been able to create test coverage output for the compiler itself.
>
> And here it is, derived from a bootcheck in grade asm_fast.gc.debug.tr
> at the standard optimization level.
Did this include the execution of the test suite or was it just the
compiler?
> Of course, many of these procedures
> *would* be executed in bootchecks in other grades and higher optimization
> levels.
>
> Unexecuted procedures:
...
> list.opt:178: pred lambda_list_opt_178/5-0
> list.opt:178: pred lambda_list_opt_178/5-0
> list.opt:178: pred lambda_list_opt_178/5-0
> list.opt:178: pred lambda_list_opt_178/5-0
...
Should we be getting things from .opt files here?
Julien.
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to: mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions: mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------
More information about the reviews
mailing list