Landon Curt Noll

Good idea @ilyakurdyukov .. thanks! We would need to run a test to determine if __int128 was supported, @ilyakurdyukov, like it done for the 64 bit code. While @pmetzger makes...

We think that calc could test for this in longbits.c without harm to systems that lack 128 bit values. BTW: There is no int128_t because of reasons that "standards" reasons...

Is there a gcc and/or clang way to use __int128 and unsigned __int128 constants, as in something like: ```c __int128 a = 0x123456789abcdef0123456789abcdef0LLL; /* ??? */ ``` Is there a...

> It also seems that recent (maybe all do that, but I didn't check) versions of GCC and Clang have this macro if __int128 is supported: It seems that is...

Here are some of our initial thoughts .. we need to think about this some more. So there status of 128-bit integers appears to be complicated: - No 128-bit constants...

A fundamental requirement to support multi-precision is that one must support these 4 BASEB operations: - Add two BASEB and get a BASEB sum with a carry bit - Subtract...

We can look into a BASEB of 64 to see if this is realistic. If it is realistic, then it needs to be optional instead of a default. This will...

FYI: The follow patch does NOT fix this problem .. it only "kicks the can down the road" far enough for calc/regeess.cal (i.e., make chk) to not trigger the reallocation...

FYI: We are using the following lines in Makefile.local to invoke clang AddressSanitizer on macOS 12.1: CFLAGS+= -fsanitize=address -fno-omit-frame-pointer LDFLAGS+= -fsanitize=address -fno-omit-frame-pointer CALC_ENV+= ASAN_OPTIONS=detect_stack_use_after_return=1

We found that gcc version 4.8.5 with libasan-4.8.5-4, only this was supported: > -fsanitize=address -fno-omit-frame-pointer On macOS 12.1 with clang version 13.0.0 (clang-1300.0.29.30), only this was supported: > -fsanitize=address -fno-omit-frame-pointer...