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

Subject: Re: [Boost-testing] pathscale 3.1 reporting problems?
From: Christopher Cambly (ccambly_at_[hidden])
Date: 2009-06-18 11:54:23

>
> Note that the test case has nothing to do with floating points.
>
My bad.  The option for integers is -qcheck=divzero.

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

We were going to submit batch new patches soon so it will included as part
of those.

>
> 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.
>
I understand but the test implies that a divide by zero will generate a
system exception for Boost.Test. The conditional code in the cpp_main for
Apple PPC just returns 1 instead of doing the actual divide by zero.  The
patch we supply can either do the same or we can add the option
(-qcheck=divzero) for this particular test so that we will generate the
system exception.  The latter seems best since it actually tests the
ability of Boost.Test to catch system exceptions on PPC platforms.

Either one is a fairly simple change.

Chris Cambly
XL C++ Compiler Development