Hi Christian,
Thanks! OK - I just know that the official Gecode 4.4.0 distribution
(MSVC 2013) works OK, and so does the debug (non-optimized) version
built from trunk using MSVC 2015.
Cheers,
Filip
Hi Filip,
This seems to be an issue with Gecode and not the compiler... Guido promised
me that he will look into floats. Real soon, he said ;-)
Cheers
Christian
--
Christian Schulte, www.gecode.org/~schulte
Professor of Computer Science, KTH, cschu...@kth.se
Expert Researcher, SICS, cschu...@sics.se
-----Original Message-----
From: users-boun...@gecode.org [mailto:users-boun...@gecode.org] On Behalf
Of Filip Konvicka
Sent: Thursday, September 17, 2015 03:39 PM
To: users@gecode.org
Subject: Re: [gecode-users] Freeze with MSVC 2015 optimized build
Sure, it's the script from my original post. I'm re-attaching it now.
I also used Gecode trunk (updated about September 1st) with Qt-5.5, built in
my Cygwin environment with MSVC 2015 RTM x64 compiler.
Thanks,
Filip
Hi Filip,
If you tell me which script you tried, I can try here (even though
Gist works for me with MSVC 2015 and Qt-5.5.0, using the trunk).
Cheers
Christian
--
Christian Schulte, www.gecode.org/~schulte Professor of Computer
Science, KTH, cschu...@kth.se Expert Researcher, SICS,
cschu...@sics.se
-----Original Message-----
From: users-boun...@gecode.org [mailto:users-boun...@gecode.org] On
Behalf Of Filip Konvicka
Sent: Thursday, September 17, 2015 03:24 PM
To: users@gecode.org
Subject: Re: [gecode-users] Freeze with MSVC 2015 optimized build
I was trying to use the Qt installer but Qt does not seem to be
visible in the cygwin environment. I'll try the source package as
you suggest, that sounds better to me.
So in the end I finished using the pre-built version of Qt and I'm now
able to run the script in Gist (Gist::dfs). The issue is still there.
I ran 'Next Solution' - this apparently runs the search in a separate
thread but never finishes (and 'Stop' does not stop the search, you
have to kill the program). Inspecting the nodes one by one freezes the
program during the 3rd expansion, and in this case the program stops
responding altogether.
So my guess is this is really some tight loop somewhere in Gecode
(maybe caused by a new optimization or bug in the new compiler?)
Cheers,
Filip
_______________________________________________
Gecode users mailing list
users@gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
_______________________________________________
Gecode users mailing list
users@gecode.org
https://www.gecode.org/mailman/listinfo/gecode-users
