Home
last modified time | relevance | path

Searched refs:unresolved (Results 1 – 3 of 3) sorted by relevance

/f-stack/dpdk/doc/guides/rel_notes/
H A Drelease_2_0.rst31 …oftware is intended to run on pre-release hardware and may contain unknown or unresolved defects or
/f-stack/freebsd/netpfil/ipfw/
H A Dip_fw_sockopt.c166 struct tid_info *ti, struct obj_idx *pidx, int *unresolved);
2724 struct obj_idx *pidx, int *unresolved) in ref_opcode_object() argument
2748 *unresolved = 1; in ref_opcode_object()
2778 int cmdlen, error, l, unresolved; in ref_rule_objects() local
2791 unresolved = 0; in ref_rule_objects()
2793 error = ref_opcode_object(ch, cmd, ti, pidx, &unresolved); in ref_rule_objects()
2800 if (unresolved != 0) { in ref_rule_objects()
/f-stack/freebsd/contrib/dev/acpica/
H A Dchanges.txt853 feature, any unresolved external declarations as well as duplicate named
919 By doing so, any unresolved external declarations as well as duplicate
1635 Fixed a possible build error caused by an unresolved reference to the
2540 iASL: Correctly handle unresolved symbols in the hardware map file (-lm
2541 option). Previously, unresolved symbols could cause a protection fault.
2542 Such symbols are now marked as unresolved in the map file.
4478 3) Update warning messages concerning unresolved method externals.
5075 Disassembler: Emit all unresolved external symbols in a single block.
10206 NULL objects - either NULL package elements or unresolved named
12160 Implemented support in the Resource Manager to allow unresolved
[all …]