nissy-core/src/solvers/h48/solve.h, branch windowsThe "engine" of nissy, including the H48 optimal solver.https://git.tronto.net/nissy-core/atom?h=windows2025-08-11T09:48:40ZWrapped pthread use in custom API2025-08-11T09:48:40ZSebastiano Trontosebastiano@tronto.net2025-08-11T08:22:56Zurn:sha1:d25f23805c6d7128b508a359d47af136dd2fd0dbAll coordinates unsigned2025-07-29T10:12:43ZSebastiano Trontosebastiano@tronto.net2025-07-29T10:12:43Zurn:sha1:ea0387796a349c91032fbcb10f50c6ad8607b0f6Trick fix2025-06-18T11:40:00ZSebastiano Trontosebastiano@tronto.net2025-06-18T11:40:00Zurn:sha1:0e334e8659deaf61c3eef57e8ccd171a5becedb3Change min depth for H48 tasks heuristic sort2025-06-18T08:14:37ZSebastiano Trontosebastiano@tronto.net2025-06-18T08:14:37Zurn:sha1:b3d1ca3d503f3d525f653067b3555e86048bfdacBig speedup for H48 solver (heuristic sort of tasks)2025-06-18T07:22:29ZSebastiano Trontosebastiano@tronto.net2025-06-18T07:22:25Zurn:sha1:5a8ca71aa8255fb76335bf41c8168cfe45eb9574More improvements to web solver2025-05-30T12:06:34ZSebastiano Trontosebastiano@tronto.net2025-05-30T12:06:34Zurn:sha1:37a2ebd4bffa99d465396fde0acfc52284ee3b7cRemoved 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.
Avoid pausing for logging only if poll_status() is null (h48 solver).2025-05-26T16:45:39ZSebastiano Trontosebastiano@tronto.net2025-05-26T16:45:39Zurn:sha1:243a852d31483d10983c50978d1d4471efd0e553
This is a small amendment to c6a77f30f64be73a5e55e06336975f2ecfbb2324,
which changed the way we log solutions while the h48 solver is running.
With the method recently introduced, the main thread checks for solutions
to log every 0.5 seconds, resulting in a possible slowdown of at most
0.5s per solve. The solutions are also logged when all worker threads are
completed. With this new method, when the poll_status() callback function
is NULL, which likely means nissy is not run interactively, we rely
only on the final log on completion of the worker threads. This means
less frequent logging, but at no performance cost.
Cleanup2025-05-25T10:38:39ZSebastiano Trontosebastiano@tronto.net2025-05-25T10:38:39Zurn:sha1:87852933851674cacbc8b2295d046831db27ab81Quick fix for bug2025-05-25T10:31:40ZSebastiano Trontosebastiano@tronto.net2025-05-25T10:31:40Zurn:sha1:2852d47c0e7b0da72259ddcec693270d52110578