Mac Intel

Mikael Pettersson <>
Sat Aug 12 23:24:00 CEST 2006


On Sat, 12 Aug 2006 12:00:59 +0100, Joel Reymont wrote:
>All this means that I need to implement floating-point exceptions,  
>right?

You really should, yes.

>Is there anything else that seems to be horribly broken?

Nothing as far as I can see.

>core, native, bench, loader, memory, process tests pass, all with  
>no_inline_fp.
>
>big tests fail, unable to allocate region.

"region"? Assuming it's Erlang being unable to allocate more
memory, you should run the same test case (big_binary) in BEAM
to determine if the problem is HiPE-related or not.

(Just c(big_binary) followed by big_binary:test() in the Erlang shell.)

>Here are the errors from running basic tests with no_inline_fp:
>
>
>./test.sh /usr/local/bin/erl "[no_inline_fp]" ""
>------------------------------------------------------------------------
>---                 Running basic_tests/test.sh                      ---
>------------------------------------------------------------------------
>
>Testing bif01.erl:
>Eshell V5.5  (abort with ^G)
>1> ok
>2>
>------------------------------------------------------------------------
>
>Testing exception01.erl:
>Eshell V5.5  (abort with ^G)
>1> Catching bad_guy(pe_badarith, e_badmatch)
>Trapping exits from spawn_link(exception01, bad_guy,  
>[pe_badarith,e_badmatch])
>
>=ERROR REPORT==== 12-Aug-2006::11:44:48 ===
>Error in process <0.36.0> with exit value: {{badmatch,b}, 

etc etc

These aren't actual errors. The test suite is checking that
exceptions etc and timeouts work, and while doing this the
system prints some error messages. Unless the test suite
reports them as failed there's nothing to worry about.



More information about the erlang-questions mailing list