Hi,
On Sat, 31 Mar 2018, Petr Skocik wrote:
The first takes symlinks into account with header file caching (I need
it with my build setup which uses a symlink in a weird way -- gcc and
clang don't have problems with it but tcc did).
Can you clarify what the problem is exactly? Thing is:
Hi,
On Sat, 31 Mar 2018, Patrick Pelissier wrote:
when compiled with TCC GIT c41caac02d53373b296ccb179b730ada62137cc0
produces the result on an linux/x86-64 platform:
N=9223372036854775810
whereas I was expecting
N=2
Indeed. Thanks for the report. Fixed in mob (f0a25ca).
Ciao,
Hi.
I've been using tcc for a while and I found some bugs and made some patches.
Please consider for inclusion.
The first takes symlinks into account with header file caching (I need
it with my build setup which uses a symlink in a weird way -- gcc and
clang don't have problems with it but tcc
The following program:
#include
#include
#include
#define N_RESET(n, i) \
(((n) & (~((ONE<< ABA_CPT)-1)) & ~(ONE << (LIMBSIZE - 1 - i))) \
|((aba_cpt_t)((n) + 1)))
#define LIMBSIZE (sizeof(limb_t) * CHAR_BIT)
#define ABA_CPT 32
