Forwarded Message
From: Balázs Sziklai
To: bug-glpk@gnu.org
Subject: glpk bug
Date: Fri, 2 Feb 2018 13:30:09 +0100
Dear GLPK Team,
I have an mip problem (see attachment) that can be solved in under a
second with glpk 4.58 but loops with glpk 4.64. That is, the gap does
not go
Hello Andrew,
when compiling GLPK-4.64 with GCC 7.2 the following warning is shown:
misc/wclique1.c: In function '_glp_wclique1':
misc/wclique1.c:121:7: warning: 'memset': specified size between
18446744071562067968 and 18446744073709551615 exceeds maximum object
size 9223372036854775807 [-Wst
On Fri, 2018-02-02 at 13:30 +0100, Balázs Sziklai wrote:
> Dear GLPK Team,
>
>
> I have an mip problem (see attachment) that can be solved in under a
> second with glpk 4.58 but loops with glpk 4.64. That is, the gap does
> not go below 0.3% no matter how much time I keep running the solver.
> Gu
Hi Heinrich,
>
> when compiling GLPK-4.64 with GCC 7.2 the following warning is shown:
>
> misc/wclique1.c: In function '_glp_wclique1':
> misc/wclique1.c:121:7: warning: 'memset': specified size between
> 18446744071562067968 and 18446744073709551615 exceeds maximum object
> size 922337203685
Please, add the missing explicit conversions to silence the warning.
Distributions like Debian want to be able to set a compiler flag which treats every warning as error.
Best regards
Heinrich
Am 02.02.18, 20:38, Andrew Makhorin schrieb:
Hi Heinrich,
>
> when compiling GLPK-4.64 with GCC 7.2
Heinrich,
> Please, add the missing explicit conversions to silence the warning.
It is a bad idea. Besides, the GNU Coding Standard recommends not to do
explicit casting if it is not needed.
Please see
http://lists.gnu.org/archive/html/bug-glpk/2017-10/msg3.html .
>
> Distributions like D
