| /freebsd/crypto/openssl/test/ssl-tests/ |
| H A D | 30-extended-master-secret.cnf | 7 test-2 = 2-disable-extended-master-secret-both-sha
8 test-3 = 3-disable-extended-master-secret-both-resume
11 test-6 = 6-disable-extended-master-secret-both-sha2
64 [2-disable-extended-master-secret-both-sha]
65 ssl_conf = 2-disable-extended-master-secret-both-sha-ssl
67 [2-disable-extended-master-secret-both-sha-ssl]
68 server = 2-disable-extended-master-secret-both-sha-server
69 client = 2-disable-extended-master-secret-both-sha-client
71 [2-disable-extended-master-secret-both-sha-server]
77 [2-disable-extended-master-secret-both-sha-client]
[all …]
|
| H A D | 19-mac-then-encrypt.cnf | 7 test-2 = 2-disable-encrypt-then-mac-both-sha
10 test-5 = 5-disable-encrypt-then-mac-both-sha2
13 test-8 = 8-disable-encrypt-then-mac-both-sha-tls1
66 [2-disable-encrypt-then-mac-both-sha]
67 ssl_conf = 2-disable-encrypt-then-mac-both-sha-ssl
69 [2-disable-encrypt-then-mac-both-sha-ssl]
70 server = 2-disable-encrypt-then-mac-both-sha-server
71 client = 2-disable-encrypt-then-mac-both-sha-client
73 [2-disable-encrypt-then-mac-both-sha-server]
79 [2-disable-encrypt-then-mac-both-sha-client]
[all …]
|
| H A D | 22-compression.cnf | 5 test-0 = 0-tlsv1_3-both-compress
9 test-4 = 4-tlsv1_2-both-compress
15 [0-tlsv1_3-both-compress]
16 ssl_conf = 0-tlsv1_3-both-compress-ssl
18 [0-tlsv1_3-both-compress-ssl]
19 server = 0-tlsv1_3-both-compress-server
20 client = 0-tlsv1_3-both-compress-client
22 [0-tlsv1_3-both-compress-server]
28 [0-tlsv1_3-both-compress-client]
115 [4-tlsv1_2-both-compress]
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/goldmont/ |
| H A D | cache.json | 140 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
152 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
229 … "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
246 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
259 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
272 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
285 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
298 … Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
311 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
324 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/goldmontplus/ |
| H A D | cache.json | 159 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
172 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
255 … "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
276 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
291 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
306 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
321 … Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
336 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
351 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
366 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /freebsd/contrib/netbsd-tests/fs/ffs/ |
| H A D | t_setquota.sh | 38 test_case_root set_${e}_${v}_"both" set_quota \
39 "set quota with both enabled" -b ${e} ${v} "both"
40 test_case_root set_new_${e}_${v}_"both" set_quota_new \
41 "set quota for new id with both enabled" -b ${e} ${v} "both"
43 "set quota for new id with both enabled, WAPBL" -bl ${e} ${v} "both"
44 test_case_root set_default_${e}_${v}_"both" set_quota_default \
45 "set default quota with both enabled" -b ${e} ${v} "both"
65 both)
121 both)
171 both)
|
| H A D | t_clearquota.sh | 34 test_case_root clear_${e}_${v}_"both" clear_quota \
35 "clear quota with both enabled" -b ${e} ${v} "both"
37 "clear quota for new id with both enabled, WAPBL" -bl ${e} ${v} "both"
58 both)
|
| H A D | t_getquota.sh | 34 test_case get_${e}_${v}_"both" get_quota \
35 "get quota with both enabled" -b ${e} ${v} "both"
55 both)
104 both)
|
| /freebsd/sys/contrib/device-tree/Bindings/arm/ |
| H A D | secure.txt | 9 space, or visible in both. (One example of that situation would be a
32 secure- bindings only need to be used where both the Secure and Normal
43 both default to "okay". This means the following combinations are
46 /* Neither specified: default to visible in both S and NS */
47 secure-status = "okay"; /* visible in both */
48 status = "okay"; /* visible in both */
49 status = "okay"; secure-status = "okay"; /* visible in both */
53 status = "disabled"; /* disabled in both */
54 status = "disabled"; secure-status = "disabled"; /* disabled in both */
|
| /freebsd/crypto/krb5/src/lib/gssapi/generic/ |
| H A D | t_seqstate.c | 45 enum width { NARROW = 0, WIDE = 1, BOTH = 2 }; enumerator
60 10, NO_REPLAY, NO_SEQUENCE, BOTH,
66 100, NO_REPLAY, DO_SEQUENCE, BOTH,
72 200, NO_REPLAY, DO_SEQUENCE, BOTH,
120 250, NO_REPLAY, DO_SEQUENCE, BOTH,
126 0, DO_REPLAY, DO_SEQUENCE, BOTH,
132 0, DO_REPLAY, NO_SEQUENCE, BOTH,
158 1000, DO_REPLAY, NO_SEQUENCE, BOTH,
177 /* Try both widths if t->wide_seqnums is both, otherwise just one. */ in main()
179 if (t->wide_seqnums != BOTH && t->wide_seqnums != w) in main()
|
| /freebsd/contrib/llvm-project/compiler-rt/lib/builtins/arm/ |
| H A D | comparesf2.S | 31 // __unordsf2(a,b) returns 0 if both a and b are numbers
63 // flag if both a and b are zero (of either sign). The shift of r3 doesn't
84 // If a and b are equal (either both zeros or bit identical; again, we're
97 // If a is smaller in magnitude than b and both have the same sign, place
98 // the negation of the sign of b in r0. Thus, if both are negative and
99 // a > b, this sets r0 to 0; if both are positive and a < b, this sets
102 // This is also done if a and b have opposite signs and are not both zero,
122 // If a is greater in magnitude than b and both have the same sign, place
123 // the sign of b in r0. Thus, if both are negative and a < b, -1 is placed
124 // in r0, which is the desired result. Conversely, if both are positive
[all …]
|
| /freebsd/contrib/bc/manuals/ |
| H A D | build.md | 26 ***WARNING***: even though `configure.sh` supports both option types, short and
27 long, it does not support handling both at the same time. Use only one type.
50 both calculators built. The default [settings][11] are `BC_BANNER=1`,
181 both compilers (`CC` and `HOSTCC`); they are supported just for legacy reasons.
187 Command-line flags for the linker. These are also passed verbatim to both
194 Libraries to link to. These are also passed verbatim to both compilers (`CC` and
218 to both, the one given to `configure.sh` takes precedence.
272 The directory to install Section 1 manpages in. Because both `bc` and `dc` are
331 be. Both options are still available for this reason.
373 Both commands are equivalent.
[all …]
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/fault/ |
| H A D | auto_spare_multiple.ksh | 40 # 8. Clear the fault on both devices
42 # 10. Rinse and repeat, this time faulting both devices at the same time
45 verify_runnable "both"
77 # hot spare to provide test coverage for both configurations.
138 # 8. Clear the fault on both devices
154 # Rinse and repeat, this time faulting both devices at the same time
160 # hot spare to provide test coverage for both configurations.
205 # 5. Clear the fault on both devices
|
| /freebsd/contrib/libarchive/libarchive/test/ |
| H A D | test_archive_match_time.c | 50 failure("Both Its mtime and ctime should be excluded"); in test_newer_time()
55 failure("Both Its mtime and ctime should be excluded"); in test_newer_time()
61 failure("Both Its mtime and ctime should not be excluded"); in test_newer_time()
107 failure("Both Its mtime and ctime should be excluded"); in test_newer_time_str()
113 failure("Both Its mtime and ctime should be excluded"); in test_newer_time_str()
120 failure("Both Its mtime and ctime should not be excluded"); in test_newer_time_str()
148 failure("Both Its mtime and ctime should not be excluded"); in test_newer_time_str()
154 failure("Both Its mtime and ctime should be excluded"); in test_newer_time_str()
161 failure("Both Its mtime and ctime should not be excluded"); in test_newer_time_str()
195 failure("Both Its mtime and ctime should be excluded"); in test_newer_time_str_w()
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/pinctrl/ |
| H A D | pinctrl-zx.txt | 5 main controller is TOP_PMM and the auxiliary one is AON_IOCFG. Both
38 'TOP pins'. For pins like KEY_ROW2, the pinmux is controlled by both
40 the pin spread in both controllers. This type of pins are called 'AON pins'.
41 Though pinmux implementation is quite different, pinconf is same for both
42 types of pins. Both are controlled by auxiliary controller, i.e. AON_IOCFG
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | cond-cmp-string.exp | 5 make: cond-cmp-string.mk:118: Comparison with '<' requires both operands 'string' and 'string' to b…
6 make: cond-cmp-string.mk:126: Comparison with '<=' requires both operands 'string' and 'string' to …
7 make: cond-cmp-string.mk:134: Comparison with '>' requires both operands 'string' and 'string' to b…
8 make: cond-cmp-string.mk:142: Comparison with '>=' requires both operands 'string' and 'string' to …
|
| H A D | opt-no-action.mk | 16 # Both of these commands are printed, but only the '+' command is run.
21 # Both of these commands are printed, but only the '+' command is run.
26 # None of these commands is printed, but both are run, because this target
32 # Both of these commands are printed, but only the '+' command is run.
|
| H A D | cond-cmp-numeric.mk | 14 # expect+1: Comparison with '>' requires both operands 'INF' and '1e100' to be numeric
20 # expect+1: Comparison with '>' requires both operands 'NaN' and 'NaN' to be numeric
25 # Since NaN is not parsed as a number, both operands are interpreted
53 # expect+1: Comparison with '<' requires both operands '123 ' and '124' to be numeric
|
| /freebsd/lib/libsys/ |
| H A D | utimensat.2 | 95 To set both a birth time and a modification time,
106 with both
111 If both
120 If both
177 or both
207 nor are both
211 nor are both
|
| /freebsd/contrib/tcp_wrappers/ |
| H A D | eval.c | 101 static char both[2 * STRING_LENGTH]; in eval_client() local
109 sprintf(both, "%s@%s", request->user, hostinfo); in eval_client()
110 return (both); in eval_client()
120 static char both[2 * STRING_LENGTH]; in eval_server() local
125 sprintf(both, "%s@%s", daemon, host); in eval_server()
126 return (both); in eval_server()
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/truncate/ |
| H A D | truncate_timestamps.ksh | 24 # Ensure both truncate(2)/ftruncate(2) update target file mtime/ctime attributes
29 # 3. Verify both mtime/ctime are updated
30 # 4. Rinse and repeat for both truncate(2) and ftruncate(2) with various sizes
33 verify_runnable "both"
67 log_assert "Ensure both truncate(2)/ftruncate(2) update target file timestamps"
|
| /freebsd/crypto/krb5/src/lib/gssapi/mechglue/ |
| H A D | g_compare_name.c | 9 * that both that copyright notice and this permission notice appear in
87 * name. (Of course we can't if both names aren't
109 * First case... both names are mechanism-specific
131 * Second case... both names are NOT mechanism specific.
154 * Second case, second sub-case... both names have
163 * Second case, third sub-case... both names have equal
164 * name_types (and both have no mech_types) so we just
|
| /freebsd/sys/sys/ |
| H A D | umtxvar.h | 38 * The umtx_key structure is used by both the Linux futex code and the
74 } both; member
132 * or umtx_lock, write must have both chain lock and
197 k1->info.both.a == k2->info.both.a && in umtx_key_match()
198 k1->info.both.b == k2->info.both.b); in umtx_key_match()
|
| /freebsd/contrib/llvm-project/clang/lib/Headers/ |
| H A D | tmmintrin.h | 198 /// both operands.
221 /// both operands.
243 /// \returns A 64-bit vector of [4 x i16] containing the horizontal sums of both
266 /// \returns A 64-bit vector of [2 x i32] containing the horizontal sums of both
293 /// sums of both operands.
319 /// sums of both operands.
342 /// of both operands.
365 /// of both operands.
388 /// of both operands.
411 /// of both operands.
[all …]
|
| /freebsd/sys/contrib/openzfs/tests/zfs-tests/tests/functional/mmp/ |
| H A D | multihost_history.ksh | 23 # zfs_multihost_history should report both writes issued and gaps
28 # 3. Check multihost_history for both issued writes, and for gaps where
33 # both vdevs will still have outstanding writes, so a skipped write entry will
41 verify_runnable "both"
|