Lines Matching defs:likely
540 ** expression that is usually false. Macro likely() surrounds
545 # define likely(X) __builtin_expect((X),1)
548 # define likely(X) !!(X)
2290 ** is running then bad things will likely happen.
4501 ** SQLITE_TRANSIENT value means that the content will likely change in
5691 ** out to disk and so if any I/O errors occur, they will likely occur
6297 ** [SQLITE_DBSTATUS options] is likely
9074 ** anybody smart enough to figure out the code is also likely smart
9141 ** windows and unix. I'm guessing that isn't likely to happen, but by
10939 #define OPFLAG_APPEND 0x08 /* This is likely to be an append */
15309 ** much more likely to break and we are much more liking to find
27758 ** or power failure will likely corrupt the database file.
28360 ** same database file at the same time, database corruption will likely
38261 ** because garbage data that appears at the end of a journal is likely
39564 ** If journal corruption occurs due to a power failure, the most likely
39566 ** It is much less likely that the two ends of the journal record will be
39568 ** though fast and simple, catches the mostly likely kind of corruption.
41267 ** with this page cache after this function returns will likely
43405 ** not the case. In this case it is likely enough that the redundant
49187 if( likely(nPayload<=pPage->maxLocal) ){
49917 ** call to btreeInitPage() will likely return SQLITE_CORRUPT.
54942 int appendBias, /* True if this is likely an append */
65823 ** will likely be much smaller since u.am.nField will likely be less than
68062 ** insert is likely to be an append.
74265 ** will likely result in an incorrect answer. So when in doubt, return
87341 int appendFlag = 0; /* True if the insert is likely to be an append */
88311 int appendBias, /* True if this is likely to be an append */
91990 ** more likely to cause a segfault than -1 (of course there are assert()
113585 ** likely to be query targets.
113706 ** argument for MERGE_COUNT of 16. Also, it is possible/likely that