Searched full:fuzzy (Results 1 – 25 of 62) sorted by relevance
123
| /freebsd/contrib/llvm-project/llvm/include/llvm/Transforms/IPO/ |
| H A D | SampleProfileMatcher.h | 25 // Sample profile matching - fuzzy match. 45 // InitialMatch stays matched after fuzzy profile matching. 47 // InitialMismatch stays mismatched after fuzzy profile matching. 49 // InitialMismatch is recovered after fuzzy profile matching. 51 // InitialMatch is removed and becomes mismatched after fuzzy profile 214 // In the scenario of profile fuzzy matching, the two sequences are the IR
|
| /freebsd/contrib/dialog/po/ |
| H A D | rw.po | 48 #, fuzzy 53 #, fuzzy 88 #, fuzzy
|
| H A D | et.po | 71 #, fuzzy 108 #, fuzzy
|
| H A D | cy.po | 72 #, fuzzy 109 #, fuzzy
|
| H A D | uk.po | 74 #, fuzzy 111 #, fuzzy
|
| H A D | rm.po | 62 #, fuzzy 75 #, fuzzy
|
| H A D | dialog.pot | 4 #, fuzzy
|
| H A D | fa.po | 21 #, fuzzy
|
| /freebsd/contrib/libxo/tests/gettext/ |
| H A D | ldns.pot | 5 #, fuzzy
|
| H A D | gt_01.pot | 5 #, fuzzy
|
| /freebsd/contrib/sendmail/src/ |
| H A D | recipient.c | 990 auto bool fuzzy; local 995 status = finduser(buf, &fuzzy, &user); 1012 if (fuzzy) 1014 /* name was a fuzzy match */ 1165 ** was found using the fuzzy matching algorithm; 1214 sm_dprintf("%s (non-fuzzy)\n", sm_strexit(status)); 1237 /* see if fuzzy matching allowed */ 1241 sm_dprintf("not found (fuzzy disabled)\n"); 1269 sm_dprintf("fuzzy matches %s\n", pw->pw_name); 1277 sm_dprintf("no fuzzy match found\n"); [all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/FileCheck/ |
| H A D | FileCheck.h | 129 /// and there might be a fuzzy match (MatchFuzzy) after the latter. 157 /// Indicates a fuzzy match that serves as a suggestion for the next
|
| /freebsd/sys/contrib/device-tree/Bindings/input/touchscreen/ |
| H A D | tsc2007.txt | 18 - ti,fuzzy: specifies the absolute input fuzz y value.
|
| H A D | ti.tsc2007.yaml | 40 ti,fuzzy:
|
| /freebsd/lib/libc/quad/ |
| H A D | fixunssfdi.c | 76 * a few fuzzy bits, but what the heck). With any luck this in __fixunssfdi()
|
| H A D | fixunsdfdi.c | 71 * a few fuzzy bits, but what the heck). With any luck this in __fixunsdfdi()
|
| /freebsd/sys/contrib/device-tree/Bindings/net/ |
| H A D | hisilicon-hns-dsaf.txt | 51 0 stands for this bit will be fuzzy matched, TCAM won't care about this bit
|
| /freebsd/contrib/llvm-project/clang/lib/StaticAnalyzer/Core/ |
| H A D | CheckerContext.cpp | 52 // similar names), only perform fuzzy name matching when it's a builtin. in isCLibraryFunction()
|
| /freebsd/sys/contrib/openzfs/config/ |
| H A D | po.m4 | 84 if LC_ALL=C $MSGMERGE --help | grep ' --no-fuzzy-matching ' >/dev/null; then 85 MSGMERGE_FOR_MSGFMT_OPTION='--no-fuzzy-matching --no-location --quiet'
|
| /freebsd/cddl/contrib/opensolaris/tools/ctf/cvt/ |
| H A D | output.c | 152 * A fuzzy match is where we have a local symbol matching the name of a 156 * A weak fuzzy match is when a weak symbol was resolved and matched to
|
| /freebsd/sys/arm/arm/ |
| H A D | trap-v6.c | 110 * operation. So, it could be really complex in SMP case and fuzzy too 651 * and fuzzy in SMP case, so maybe in future standard fault mechanism
|
| /freebsd/contrib/llvm-project/llvm/lib/Transforms/IPO/ |
| H A D | Internalize.cpp | 204 // For llvm.compiler.used the situation is a bit fuzzy. The assembler and in internalizeModule()
|
| /freebsd/contrib/googletest/docs/ |
| H A D | gmock_for_dummies.md | 407 it as many times. More importantly, a cardinality can be "fuzzy", just like a 415 We've seen `AtLeast(n)` as an example of fuzzy cardinalities earlier. For the
|
| /freebsd/crypto/krb5/src/util/ |
| H A D | cstyle-file.py | 232 # This is intentionally pretty fuzzy so that we catch the whole scanf
|
| /freebsd/lib/libpmc/pmu-events/arch/powerpc/power9/ |
| H A D | other.json | 60 … in an active fuzzy prefetch stream. The stream could have been allocated through the hardware pre… 520 … in an active fuzzy prefetch stream. The stream could have been allocated through the hardware pre…
|
123