nissy-core/tools/tool.h, branch masterThe "engine" of nissy, including the H48 optimal solver.https://git.tronto.net/nissy-core/atom?h=master2026-04-06T13:55:33ZMake the project build with Microsoft's broken C compiler.2026-04-06T13:55:33ZSebastiano Trontosebastiano@tronto.net2026-04-06T13:55:33Zurn:sha1:fc41f7917531693680b5baf71ffe38c47333fe84
MSVC is not fully C11-compliant, even when compiling with /std:c11.
Some changes were needed to make the codebase compatible. Notably, the
notation a[static N] and a[n] for function parameters of array type is
not supported, so that had to be hidden behind a macro. Atomic types
are also an experimental feature, apparently, but at least they work
with the correct compiler flag.
One thing that MSVC does well, however, is warning on integer conversions
on /W4 level. I am not sure if Clang and GCC have something similar,
so I took this chance to fix some of these.
Fix alignment2025-12-17T16:36:16ZSebastiano Trontosebastiano@tronto.net2025-12-17T16:36:16Zurn:sha1:ec9593e2ff0856d78b37df3a977a753be82bfddcMore build.bat options2025-08-13T15:38:21ZSebastiano Trontosebastiano@tronto.net2025-08-13T15:38:21Zurn:sha1:9b94c7d039341afb8609075da0ce52a7a7aa705aAdded DRFIN solver2025-08-05T07:04:00ZSebastiano Trontosebastiano@tronto.net2025-08-05T07:04:00Zurn:sha1:3e7bb9b87ef9b47d8f643dbcae19a64ddbc81dbbFixed table name in tools2025-07-31T11:42:33ZSebastiano Trontosebastiano@tronto.net2025-07-31T11:41:29Zurn:sha1:474039de7af2cee7fa309e06a5c4e75b81f220adRefactored checkdata2025-05-19T15:45:14ZSebastiano Trontosebastiano@tronto.net2025-05-19T15:45:14Zurn:sha1:62d87e063318cc4c842b1b2d8c184f48aeaf6659
Relevant changes include:
- Changed the signature of nissy_checkdata().
- Removed expected_distribution.h from tools; this data is now included
in each solver's src/ code.
- Removed distribution check for cocsep; may add back later.
Refactor solver dispatch and checkdata2025-05-18T06:48:13ZSebastiano Trontosebastiano@tronto.net2025-05-18T06:48:13Zurn:sha1:8b94d135429a9f3253cc7f25a1453b412065c4a0Always use unsigned char * for data buffers2025-04-21T12:44:07ZSebastiano Trontosebastiano@tronto.net2025-04-21T12:33:01Zurn:sha1:510a7471348788fccba6b7c4b9f7b7cc9aee6ba9
Before this commit I was inconsistently using one of void *, char *
and uint8_t *.
Restore logging to stderr for tools2025-04-17T12:36:47ZSebastiano Trontosebastiano@tronto.net2025-04-17T12:36:47Zurn:sha1:c182f3f16e56e9533060ffa06b25391e239a28eeBetter logging function2025-04-15T13:51:40ZSebastiano Trontosebastiano@tronto.net2025-04-15T13:51:40Zurn:sha1:b25a939e2d8b045c083caf3264c4e5aac1cf88fb
Now it is possible to provide some data together with the logging function.
This is useful for example in C++, where I can now provide an arbitrary
callable object as data, and a simple wrapper function that call the
callable object as logging function.