Dan is right. I think I'd calling this a clang bug. On Feb 12, 2015 9:06 AM, "Dan Kennedy" <danielk1...@gmail.com> wrote:
> On 02/12/2015 09:02 PM, Jens Miltner wrote: > >> Hi, >> >> I'm getting the following two warnings when compiling sqlite3.c with the >> latest clang tools: >> >> sqlite3.c:116769:39: warning: code will never be executed >>> [-Wunreachable-code] >>> if( pTerm->wtFlags & TERM_VNULL ) continue; >>> ^~~~~~~~ >>> sqlite3.c:116716:39: warning: code will never be executed >>> [-Wunreachable-code] >>> if( pTerm->wtFlags & TERM_VNULL ) continue; >>> ^~~~~~~~ >>> 2 warnings generated. >>> >>> (This is for SQLite version 3.8.8.2). >> >> >> From the code, I don't immediately see why the compiler would think this >> code will never be executed, so I thought I'd bring it up with you guys. >> > > > Unless you have defined SQLITE_ENABLE_STAT4 (or STAT3), TERM_VNULL is > defined as 0: > > http://www.sqlite.org/src/artifact/d3633e9b59210324?ln=273-277 > > Dan. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
