D. Richard Hipp <d...@...> writes: ...snip.... > > Many of the warnings you mention could be suppressed by initializing > some variables. But those initializations are technically unnecessary > and thus slow things down. (Most will probably make no measureable > difference in speed, but an unnecessary initialization in an > inner loop can make a big difference.) So I am disinclined to > fix them. > > Note that it is exceedingly unlikely that any of the warnings > mentioned could be a real bug, since if that were the case the > warning would appear with the -O0 option in addition to the -O2 > option. Since the warnings only appear with -O2, they are > probably just optimizer artifacts. >
Actually, according to the GCC documentation, GCC only detects use of uninitialised variables if the optimiser is turned on. Hence using -O0 (=opt off) does not throw up those warnings since the usage is not checked. Regards, MikeW PS. yes, I am looking at cleaning up our SQLite build output ! _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
