I'm all with you, those should be addressed in the source, sometimes by casting
things you know for sure,
sometimes by redefining things.
all my experience in c++ over 30+ years is that "no warning is without some
sense", but I always succeed to shut them off.
Xtian.
On 2017-01-16 23:10, Xiao
In addition, there is one more warning/error.
g++ -DHAVE_CONFIG_H -I. -I..-Werror -Wall -I sql -I/sandbox/pkg/lib/include
-I/sandbox/pkg/include -rdynamic -Wno-maybe-uninitialized -march=native -O3
-pipe -I/sandbox/pkg/include -MT apl-SymbolTable.o -MD -MP -MF
.deps/apl-SymbolTable.Tpo -c
Not sure if it's another gcc unrolling bug.
Using gcc 6.2.0
g++ -DHAVE_CONFIG_H -I. -I..-Werror -Wall -I sql -I/sandbox/pkg/lib/include
-I/sandbox/pkg/include -rdynamic -march=native -O3 -pipe
-I/sandbox/pkg/include -MT apl-Bif_F12_SORT.o -MD -MP -MF .deps/ap
l-Bif_F12_SORT.Tpo -c -o apl-Bi
Looks like a gcc loop unrolling bug.
I have another issue.
cc1plus: warnings being treated as errors
In file included from
Quad_SQL.
Hi Xiao-Yong,
I believe the warning is equally bogus as the one below.
It is true that other.rho_rho is int32_t while Shapeitem
is int64_t, but
the comparison in the loop() macto is between two int64_ts.
And has
nothing to do with array sub
I'm seeing the same array subscript errors with gcc 4.4.7 here.
g++ -DHAVE_CONFIG_H -I. -I..-Werror -Wall -I sql -I/usr/include -rdynamic
-mcpu=power7 -mtune=power7 -O3 -fno-math-errno -funsafe-math-optimizations
-fno-rounding-math -fno-signaling-nans -fcx-limited-range -pipe -MT
apl-Arra