gecode icon indicating copy to clipboard operation
gecode copied to clipboard

Generic Constraint Development Environment

Results 50 gecode issues
Sort by recently updated
recently updated
newest added

In GeCode 6.3.0 used through MiniZinc IDE, the GeCode solver hangs and crashes after a while for this code: ``` float: x = 1.1e10; var float: y; constraint x >...

**Description** There is a memory leak at Engine in a multi-threading context when the following conditions are met: - Thread number > 1 - CSP having more than one solution...

bug

Hello, This patch implements a stronger pruning technique for the BinPacking constraint. It leverages tighter lower bounds based on Dual-Feasible Functions. This approach was presented at CP 2024 in the...

Built with clang-18 + `-O2 -UNDEBUG` ``` [0/1] Running tests... Test project /-build/build/stage-2/minizinc-meta/gecode Start 1: test 1/1 Test #1: test .............................Subprocess aborted***Exception: 0.57 sec Int::Arithmetic::Mult::XYZ::Bnd::C ++ Int::Arithmetic::Mult::XYZ::Dom::A gecode-test: //gecode/test/int.cpp:289: void...

Ensure that it gets built when testing is enabled, and that CMake actually uses said executable target, and not some binary. That being said, the test does not pass with...

I've built gecode from `release/6.3.0` branch (specifically, f7f0d7c273d6844698f01cec8229ebe0b66a016a), plus libminizinc 2.8.5 release, using clang-18 `-O2 -UNDEBUG`. At least one minizinc test has issues, the last output is: (only one test...

In bc31c318b73b47a085551fc3a6fa70dba89dad28 Gecode's timer handling was unified to std::chrono::steady_clock. This removed the need for checking at build time for which timer to use and AC_GECODE_TIMER M4 macro was removed that...

https://github.com/Gecode/gecode/blob/027c57889d66dd26ad8e1a419c2cda22ab0cf305/gecode/kernel/data/array.hpp#L1571 This line will throw an unexpected exception if `aa` is empty.

In some build configurations, the use of `WIN32` fails and these were the only locations in the code using that formulation. Use `_WIN32` instead.

By using `file(CONFIGURE)` instead of `file(WRITE)`, the file output will only be written if it has changed. This allows for running `cmake` to pick up other (possible) changes without triggering...