[m-rev.] for review: disable tracing for slice tools

Ian MacLarty maclarty at csse.unimelb.edu.au
Mon Oct 16 17:06:30 AEST 2006


On Thu, Oct 05, 2006 at 04:36:00PM +1000, Ian MacLarty wrote:
> For review by Zoltan.
> 
> Notes:
> 
>   * This diff allows "tools/bootcheck --coverage-test" to build stage 2
>     with the stage 1 compiler built in grade asm_fast.gc.decldebug.
>     (stage 3 is still being built).
> 
>   * I didn't need to disable tracing for any library modules.
>     Disabling tracing for the mdbcomp modules was sufficient.
> 
> Questions:
> 
>   * Do we still need to copy the slice directory when building stage 2?
>     I'm guessing that the reason it was copied was to test that it could
>     be built with the workspace compiler (since the stage 1 slice directory 
>     was built with the installed compiler).  If this is the case is it
>     now okay to not copy the stage 2 slice directory in the bootcheck
>     script when coverage testing?
> 
> Estimated hours taken: 1
> Branches: main
> 
> Copy the mdbcomp modules used by the slice tools to the slice
> directory before building the slice tools.
> 
> Disable tracing for all modules in the slice directory so that mtc_union
> doesn't blow its stack when called during coverage testing of the compiler.
> 

I've committed this now.

Ian.
--------------------------------------------------------------------------
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