getting started with the test_c & test_i

Sergey.Bochkanov · **Joined:** Fri May 07, 2010 7:06 am **Posts:** 906

I think that I've isolated this bug. I'll make some additional tests during Monday, but I think that only ap.cpp have to be fixed. I'll e-mail you when patch will be ready. Hope it will be Monday or Tuesday.

Sergey.Bochkanov · **Joined:** Fri May 07, 2010 7:06 am **Posts:** 906

I think that problem is solved now. Only ap.cpp/ap.h were changed. I've posted fixed files (see attachment), can you try compiling your project once more with -O3?

rhine · **Joined:** Fri Oct 01, 2010 2:25 am **Posts:** 7

yes. it all works now.
thanks a lot for the fix!
rhine.

Sergey.Bochkanov · **Joined:** Fri May 07, 2010 7:06 am **Posts:** 906

That was very strange bug in GCC - for some reason following code for accessing first 4 bytes of double precision number worked incorrectly

Code:

double val = something;
ae_int32_t first_4_bytes = ((ae_int32_t*)(&val))[0]; // works incorrectly under -O3 and old GCC

so I was forced to replace it by

Code:

union _u_type
{
double val;
ae_int32_t p[2];
} u;
u.val = something;
ae_int32_t first_4_bytes = u.p[0] ; // works correctly under -O3

mm83 · **Joined:** Sat Nov 20, 2010 12:55 pm **Posts:** 1

Hi there,
Great toolbox!
I'm still having problem running "test_i". Could someone explain to me (or better post a piece of code) how do I define "AE_USE_ALLOC_COUNTER" so it will work?

Many thanks

Sergey.Bochkanov · **Joined:** Fri May 07, 2010 7:06 am **Posts:** 906

You should define at at global level using corresponding compiler directive. Just define AE_USE_ALLOC_COUNTER, and that should be enough

forum.alglib.net

Forum rules

getting started with the test_c & test_i

Who is online