Lines Matching defs:likely
514 ** expression that is usually false. Macro likely() surrounds
519 # define likely(X) __builtin_expect((X),1)
522 # define likely(X) !!(X)
1494 ** New verbs are likely to be added in future releases of SQLite.
1995 ** is running then bad things will likely happen.
3952 ** SQLITE_TRANSIENT value means that the content will likely change in
5010 ** out to disk and so if any I/O errors occur, they will likely occur
5602 ** Additional options will likely appear in future releases of SQLite.
7931 ** anybody smart enough to figure out the code is also likely smart
7998 ** windows and unix. I'm guessing that isn't likely to happen, but by
9712 #define OPFLAG_APPEND 0x08 /* This is likely to be an append */
12958 ** much more likely to break and we are much more liking to find
24437 ** or power failure will likely corrupt the database file.
31574 ** because garbage data that appears at the end of a journal is likely
32583 ** If journal corruption occurs due to a power failure, the most likely
32585 ** It is much less likely that the two ends of the journal record will be
32587 ** though fast and simple, catches the mostly likely kind of corruption.
33835 ** with this page cache after this function returns will likely
38470 if( likely(nPayload<=pPage->maxLocal) ){
39208 ** call to btreeInitPage() will likely return SQLITE_CORRUPT.
44042 int appendBias, /* True if this is likely an append */
54349 ** will likely be much smaller since u.am.nField will likely be less than
56422 ** insert is likely to be an append.
61479 ** will likely result in an incorrect answer. So when in doubt, return
74187 int appendFlag = 0; /* True if the insert is likely to be an append */
75143 int appendBias, /* True if this is likely to be an append */
78622 ** more likely to cause a segfault than -1 (of course there are assert()
97999 ** likely to be query targets.
98120 ** argument for MERGE_COUNT of 16. Also, it is possible/likely that