Searched full:disambiguate (Results 1 – 25 of 33) sorted by relevance
12
12 firmware version. The program field is used to disambiguate two
102 value. This is used to disambiguate interfaces which might be
52 readarray -t matches < <(git rev-parse --disambiguate="$commit_id" 2>/dev/null)194 if [ "$(git rev-parse --disambiguate="$1" 2>/dev/null | wc -l)" -eq 0 ]; then
23 # It's used to help disambiguate any duplicate symbol names, which can occur
16 * different set of fields we will need to figure out how to disambiguate.
23 typically refer to this instruction set as eBPF to disambiguate it from cBPF.
26 * specific collision record to disambiguate the new entry from the existing one. Index entries are
20 terminology is designed to disambiguate software's view of execution
13 disambiguate the hardware view of these physical components/assemblies
176 * @uid: ACPI Unique ID, can be used to disambiguate matches.
61 * which is why I chose TRIM here, to disambiguate. */
296 * we can still disambiguate them.499 * needed to disambiguate references from split BTF.
260 be used to disambiguate functions of the same name. This is not the
112 * in order to disambiguate certain connect race conditions.
384 * These bits disambiguate different calling conventions that share an
1231 * event ID. e.g. Intel PT uses this record to disambiguate PEBS-via-PT
241 context and disambiguate the reference.
597 /* cannot disambiguate full vs empty due to head/tail size */ in io_register_pbuf_ring()
27 name as necessary to disambiguate it from others is necessary. Note that options are case-sensitiv…
593 * Currently, there is not enough information to disambiguate different PEBS
108 fully disambiguate branch address and uses the offset for prediction,
310 disambiguate timestamps and SOF_TIMESTAMPING_OPT_TSONLY to operate
1177 disambiguate both ABIs and allow for backward compatibility support
1100 * Used only when available, may not be enough to disambiguate