Jang Ryeol

Actually, it is gcc optimization problem rather than NDEBUG symbol. There is a patch for this in the mailing list. The case statement fails to match as the braces are stripped when the configure.in is converted to the configure script. This is bad, as the configure script then decides to set GCC to false, and no optimisation flags are applied. Signed-off-by: Joel Stanley <joel@...> --- v2: The first fix was incorrect, as I was testing the changes by hacking configure not configure.in. When generating...

Actually, it is gcc version parsing problem rather than NDEBUG symbol. There is a patch for this in the mailing list. The case statement fails to match as the braces are stripped when the configure.in is converted to the configure script. This is bad, as the configure script then decides to set GCC to false, and no optimisation flags are applied. Signed-off-by: Joel Stanley <joel@...> --- v2: The first fix was incorrect, as I was testing the changes by hacking configure not configure.in. When generating...

Actually, it is gcc version parsing problem rather than NDEBUG symbol. There is a patch for this in the mailing list. > Signed-off-by: Joel Stanley <joel@...> > --- > v2: The first fix was incorrect, as I was testing the changes > by hacking configure not configure.in. When generating configure, > single quotes are removed. > > This has been tested on x86_64 and ppc64le. > > configure.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/configure.in b/configure.in > index cea313d..aee44a6...

It seems gcc is the problem, not NDEBUG symbol. Still, r6323 is the problematic one. In r6323, gcc version checking code was added which disables all gcc optimizations when gcc version is badly formatted. Unfortunately, whoever committed this failed to correctly catch 'badly formatted one', thus every gcc gets no optimizations. Actually there was a word warning this... AC_MSG_RESULT(unknown compiler version pattern, playing safe and disabling gcc optimisations... ${GCC_version}) But sadly the configure...

It seems gcc is the problem, not NDEBUG symbol. In r6323, gcc version checking code was added which disables all gcc optimizations when gcc version is badly formatted. Unfortunately, whoever committed this failed to correctly catch 'badly formatted one', thus every gcc gets no optimizations. Actually there was a word warning this... AC_MSG_RESULT(unknown compiler version pattern, playing safe and disabling gcc optimisations... ${GCC_version}) But sadly the configure script could not print "disabling...

It seems gcc is the problem, not NDEBUG symbol. In r6323, gcc version checking code is added which disabled all gcc optimizations when gcc version is badly formatted. Unfortunately, whoever committed this failed to correctly catch 'badly formatted one', thus every gcc gets no optimizations. Actually there was a word warning this... AC_MSG_RESULT(unknown compiler version pattern, playing safe and disabling gcc optimisations... ${GCC_version}) But sadly the configure script could not print "disabling...

It seems gcc is the problem, not NDEBUG symbol. In r6323, gcc version checking code is added which disabled all gcc optimizations when gcc version is badly formatted. Unfortunately, the configure script cannot correctly parse gcc version on CentOS 7, GCC 4.8.5. Actually there was a word warning this... AC_MSG_RESULT(unknown compiler version pattern, playing safe and disabling gcc optimisations... ${GCC_version}) But the configure script could not print "playing safe.." part because of the comma.