nissy-core/src/solvers/coord/common.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.
Add coordinate solvers for corners2025-12-19T06:32:09ZSebastiano Trontosebastiano@tronto.net2025-12-19T06:32:09Zurn:sha1:de04d37e8520079f5bba3b1a87d42313297543dbAdded HTR solver2025-08-06T14:52:12ZSebastiano Trontosebastiano@tronto.net2025-08-06T14:34:21Zurn:sha1:57a7520545134ab95f7bb0397dcbe991c906a3e9Added DRFIN solver2025-08-05T07:04:00ZSebastiano Trontosebastiano@tronto.net2025-08-05T07:04:00Zurn:sha1:3e7bb9b87ef9b47d8f643dbcae19a64ddbc81dbbadded drslice coordinate2025-07-30T14:10:29ZSebastiano Trontosebastiano@tronto.net2025-07-29T14:57:21Zurn:sha1:6cf7cd87a90a1314332aace1d25b9c0f230dc227Make failed assert exit immediately2025-07-28T11:52:00ZSebastiano Trontosebastiano@tronto.net2025-07-28T11:52:00Zurn:sha1:7f24b27652ee6fa84e38f181cea57f319af0c204Working drslice (same results as nissy-classic)2025-07-17T05:57:18ZSebastiano Trontosebastiano@tronto.net2025-07-17T05:57:18Zurn:sha1:5e741a00a1350477c7d8778cb466c8efa27b152dRemoved VLA notation from function parameters.2025-05-27T07:03:51ZSebastiano Trontosebastiano@tronto.net2025-05-27T07:03:51Zurn:sha1:7c934801f88c640970ad41b5ddd39f4e39609f28
I found out that this gives undefined behavior when then size is 0.
Better not to have it at all, it is confusing for other developers anyway.
Always 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 *.
Added dreo coordinate solver2025-04-02T12:33:21ZSebastiano Trontosebastiano@tronto.net2025-04-02T12:33:21Zurn:sha1:c5a6ff0443fc9e5e890fe72cb13ea78d4fe2bbcb