Re: [Boost-testing] pathscale 3.1 reporting problems?

Subject: Re: [Boost-testing] pathscale 3.1 reporting problems?
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2009-06-17 14:22:30

Christopher Cambly <ccambly <at> ca.ibm.com> writes:

> This testcase appears to assume that all hardware will 
> generate an exception on a divide by zero. Â I believe 
> that the PPC hardware itself does not raise an exception 
> on a divide by zero.

What does it do in case of integer being divided by zero?

> The compiler can insert special code around the divide by 
> zero to cause an exception similar to what is expected by 
> this testcase but that is not the default of the hardware 
> or the compiler.In a patch that we provided for Boost 
> 1.34.1 we added an option (-qflttrap=zerodivide) to the 
> Jamfile that would generate the behaviour expected by this 
> testcase. Â 

Note that the test case has nothing to do with floating points.

> However, the change was never propagated to the Boost 
> development line which is why the test still fails for us.

Would you like me to add this to Jamfile? can you post patch again?

> Â Certainly, the test could be marked as a known failure 
> but the underlying assumption of the test that all 
> hardware/software will fail on a divide by zero is false.

This is incorrect statement. Test does not have these underlying 
assumptions. The module just tests that Boost.Test is able to catch and properly
report an exception in case it's actually being generated.
Overall the test is expected to fail in this case. We can mark the test as
expected to pass in particular configuration.

Gennadiy