[mercury-users] asm_fast(.gc) for intel/mac?

[Julien Fischer]

On Tue, 6 Feb 2007, Ben Schmidt wrote:

> In reg.gc I get the following failures:
>
> debugger/cmd_quote
> debugger/io_tab_goto
> debugger/tabled_read
> debugger/tabled_read_decl
> debugger/interactive
> debugger/declarative/tabled_read_decl
> debugger/declarative/tabled_read_decl_goto
> general/string_format/string_format_o
> tabling/loopcheck
> tabling/loopcheck_nondet
> tabling/tc_loop
> tabling/tc_memo
> tabling/tc_memo2
> valid/ho_and_type_spec_bug
> valid/foreign_type_spec
>
> The debugger ones seem to be simply that a format function somewhere 
> interprets/outputs signed rather than unsigned hexadecimal for a stack of 
> pointers; I suspect not a Darwin bug, but a missing format specifier in the 
> debugger code somewhere. The string_format one is a bug in the Darwin C 
> library the same as in a few other systems (should probably tell the test 
> suite about that). Tabling ones seem to just contain complaints that stack 
> traces are not available

The tabling tests should be run with MERCURY_SUPPRESS_STACK_TRACE=yes
(which is what the bootcheck script does).  The tabling tests should
then pass.

Julien.
--------------------------------------------------------------------------
mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au
--------------------------------------------------------------------------