Searched refs:understood (Results 1 – 25 of 63) sorted by relevance
123
111 bool understood = true; in getMatchingStatuses() local127 understood = false; in getMatchingStatuses()140 return understood; in getMatchingStatuses()
25 particular item, but the full implications must be understood and33 implications should be understood and the case carefully weighed
3 ; Check that metadata encoded in 3.5 is correctly understood going forward.
20 // <rdar://problem/8808566> Static analyzer is wrong: NSWidth(imgRect) not understood as unconditio…
31 The regular expression syntax understood by this package when parsing with the Perl flag is as foll…
301 * pragma understood my MS compiler which enables a conditional link with313 * pragma understood my MS compiler which enables a conditional link with
13 # well understood memory formats.
29 # understood.
28 # understood.
26 \Var{lo} and \Var{hi} should be understood as a hint:
41 operation has a version or a format that is not understood by
69 version or format that is not understood by \Prog{libunwind}.
103 version or format that is not understood by \Prog{libunwind}.
40 # understood.
42 # understood.
13 ; CHECK: remark: source.cpp:5:9: loop not vectorized: loop control flow is not understood by vector…
73 which might not be understood by the gdbserver of gdb).
162 # have agreed and understood, that there is no warranty whatsoever for
6 ; understood the mechanisms by which this bug occurs, so perhaps there's further
72 info <../SourceLevelDebugging.html>`_ which is understood by common
156 The following options are understood:
211 that you have read, understood, and will comply with the following terms and
349 by commas. The following identifiers are understood:
109 The object types currently understood by \verb|ip| are:1155 full list of types understood by Linux-2.2 is:1233 the longest match is understood as: First, compare the TOS1588 so that it can be understood easily. F.e.\1917 What happened? Router 193.233.7.254 understood that we have a much