Searched refs:recognized (Results 1 – 25 of 576) sorted by relevance
12345678910>>...24
5 ; CHECK-LIST: llvm-lto: error loading file '{{.*}}/Inputs/empty.bc': The file was not recognized as…8 ; CHECK-THIN: llvm-lto: error loading file '{{.*}}/Inputs/empty.bc': The file was not recognized as…
4 ; Should not crash when the processor is not recognized and the9 ; ERROR: 'unknown' is not a recognized processor for this target (ignoring processor)
34 # Iff a copyright statement is recognized in a file and the final44 # statement is recognized.47 # order to be recognized. For example, each of these is fine:60 # However, the following format is not recognized because the line67 # a non-matching copyright statements would be recognized.70 # to be recognized are:103 # 1. If UPDATE_COPYRIGHT_FORCE=1, a recognized FSF copyright statement
12 ; CHECK-NOT: is not a recognized processor for this target13 ; INVALID: {{.+}} is not a recognized processor for this target
15 ; CHECK-NOT: {{.*}} is not a recognized processor for this target16 ; INVALID: {{.*}} is not a recognized processor for this target
43 // Make sure the declaration of -test was recognized.45 // Make sure the declaration of NS::foo was recognized.
3 // FIXME: We could do much better with this, if we recognized
286 bool recognized; in _mesa_one_time_init_extension_overrides() local305 recognized = true; in _mesa_one_time_init_extension_overrides()307 recognized = false; in _mesa_one_time_init_extension_overrides()313 if (!recognized && enable) { in _mesa_one_time_init_extension_overrides()
2 UNKNOWN_FILE_TYPE: {{.*}}invalid-input.test: The file was not recognized as a valid object file
2 MALFORMED: The file was not recognized as a valid object file
6 UNKNOWN_FILE_TYPE: '{{.*}}invalid-input.test': The file was not recognized as a valid object file
8 ENG are recognized types. If not specified, PEM is assumed.
6 subset of the states unterstood by "conntrack" are recognized: \fBINVALID\fP,
6 by symbolic name. The list of recognized options can be obtained by calling
11 recognized TOS names can be obtained by calling iptables with \fB\-m tos \-h\fP.
18 # CHECK: '+fp' is not a recognized feature for this target (ignoring feature)
7 Standard character set names like "UTF-8" are NOT recognized.18 - All IANA character set names are recognized in a coding- and case-insensitive
3 ; Check that loads from calloc are recognized as being zero.
5 ; CHECK-NOT: not a recognized processor for this target
126 // Test that hard-coded Microsoft _wassert name is recognized as a noreturn136 // Test that hard-coded Android __assert2 name is recognized as a noreturn
5 ; should be recognized as a factor in the last fsub, so we should
28 Device recognized as MTP, no further probing.
34 self.a.x = 0; // every dealloc must zero out its own ivar. This patter is not recognized.