On Sep 28, 2009, at 10:15 AM, Dr. David Kirkby wrote:
> Roger Binns wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Dr. David Kirkby wrote:
>>> "sqlite3.c", line 18731: warning: integer overflow detected: op "<<"
>>> "sqlite3.c", line 18748: warning: integer overflow detected: op "<<"
>>> "sqlite3.c", line 32546: warning: statement not reached
>>> "sqlite3.c", line 69160: warning: integer overflow detected: op "<<"
>>
>> http://www.sqlite.org/faq.html#q17
>>
>> Roger
>
> Thank you.
>
> I understand you can't fix these warnings since you don't have
> access to
> such machines. Would you like access? If so, I can give you access
> to a
> 16-core Sun T5240 at the university of Washington, with runs Solaris
> 10
> update 7 (latest version). It also has the Sun compiler installed (not
> quite the latest I must admit), though I could easily change that.
>
We probably don't need your compiler to "fix" the warnings. Either
the warnings actually point to bugs, or they do not. If they do, we
will fix the bug. If the do not (the likely case, based on historical
trends) then we will do nothing because warnings are not errors but
misguided efforts to "fix" warnings often introduce errors.
But as it stands now, we cannot even evaluate the warnings to
determine whether or not they are bugs because you haven't told us
what version of SQLite you are attempting to compile so the line
numbers are meaningless. (In a 100,000-line source file, line numbers
shift drastically from day to day.) We want to know the value of the
following two C preprocessor macros:
SQLITE_VERSION
SQLITE_SOURCE_ID
D. Richard Hipp
d...@hwaci.com
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
