hello xX_Pokeman2003_Xx I get this warnings, I thinks that it explain the problem code.c: In function 'main': code.c:37:94: warning: '__builtin_memset' writing 256 bytes into a region of size 32 [-Wstringop-overflow=] 37 | *(char**)((uint8*)POINTERS$0 + ((int64)I$1 << (3ll & 63ll))) = (char*)0ul...

hello Tonigau :) a couple of errors in ezySVG.bi in functions SVG_Polygon and SVG_PolyLine the array PolyBB is an array of Long but in the function SVG_GetPolyMid it's an array of integer in TestSVG_1.bas line 202 you have SVG_Image(550, 280, 150, 200, "xMidyMid", FilePath +FileName, 0) bu...

very impressive!
thanks for sharing

SARG
yes!, that silenced the warnings
now it builds without a single warning

that warning doesn't make sense to me, I don't think it's worth the trouble to silence it
thanks SARG for looking into it

@SARG 2 more warnings that need to be fixed src/gfxlib2/gfx_bsave.c: In function 'save_bmp': src/gfxlib2/gfx_bsave.c:138:64: warning: 'calloc' sizes specified with 'sizeof' in the earlier argument and not in the later argument [-Wcalloc-transposed-args] 138 | paltmp = (unsigned int *)calloc(sizeof(u...

thank you SARG
I was not sure that movsd and movsl were equivalent, google didn't help

hello SARG
when building FB with gcc-13+ you get warnings like Warning: found `movsd'; assuming `movsl' was meant
I think that the culprit are the FB_MEMCPY functions defined in FB.h
how would you change those functions in order to get rid of those warnings?

I like to test the latest toolchains together with the latest work in progress FB, I do most of my tests in 64-bit but today I wanted to see the performance difference between 32 and 64-bit only to find that my program would crash with the error 0xC0000005 the test program uses 4 strings 10100 in si...

I changed my code, instead of a function to set the precision I changed the initializer to take a precision argument, the FB code needs to start with these 2 lines const dec_float_digits_precision = 64 #Include "DecFloatC.bi" there are no problems with shared variables :D never knew that F...

in the file DecFloatC.c I edited int NUMBER_OF_DIGITS=64; int NUM_DIGITS=64; int NUM_DIGITS2; int NUM_DWORDS=8; int NUM_BYTES=32; int EXTRAWORDS = 0; and put the following in the DecFloat_init function printf("NUM_DWORDS + 1 + EXTRAWORDS=%d\n", NUM_DWORDS + 1 + EXTRAWORDS); and run this FB...

I wanted to be able to set the precision at runtime, that's why I went this route what puzzles me is why the following doesn't help const digits_precision = 128 dim shared as long NUMBER_OF_DIGITS, NUM_DIGITS, NUM_DWORDS, NUM_BYTES scope dim as long n = digits_precision / 8 if (8 * n) = digits_preci...

@SARG
it looks like a terrible blunder on my part
NUM_DWORDS is set when when DecFloat_Set_Digits is called but apparently the overloaded functions/operators are set when NUM_DWORDS hasn't been defined yet
I will have rethink the whole thing

I found the culprit Operator Decfloat.let ( Byref rhs As Decfloat ) this.DecNum.sign=rhs.DecNum.sign this.DecNum.exponent=rhs.DecNum.exponent memcpy( this.DecNum.mantissa, rhs.DecNum.mantissa, NUM_BYTES ) End Operator changing it to the following and all is well, need to make sure and replace all me...

@SARG
I changed the exponent in the bi to long because the following didn't work as expected in 32-bit thanks guy for looking into the problem