| /freebsd/lib/libpmc/pmu-events/arch/x86/goldmont/ |
| H A D | frontend.json | 43 …"BriefDescription": "References per ICache line. This event counts differently than Intel processo…
48 …undary, or when a branch target is to a new line.\r\nThis event counts differently than Intel proc…
53 … ICache line that are available in the ICache (hit). This event counts differently than Intel proc…
58 …to a new line, and that cache line is in the ICache. This event counts differently than Intel proc…
63 …he line that are not available in the ICache (miss). This event counts differently than Intel proc…
68 … new line, and that cache line is not in the ICache. This event counts differently than Intel proc…
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/goldmontplus/ |
| H A D | frontend.json | 51 …"BriefDescription": "References per ICache line. This event counts differently than Intel processo…
58 …undary, or when a branch target is to a new line.\r\nThis event counts differently than Intel proc…
63 … ICache line that are available in the ICache (hit). This event counts differently than Intel proc…
70 …to a new line, and that cache line is in the ICache. This event counts differently than Intel proc…
75 …he line that are not available in the ICache (miss). This event counts differently than Intel proc…
82 … new line, and that cache line is not in the ICache. This event counts differently than Intel proc…
|
| /freebsd/contrib/arm-optimized-routines/ |
| H A D | README.contributors | 28 - On aarch64 the tests must pass. If the code may behave differently under
43 - Unless otherwise required differently by the sub-project, follow the
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | varmod-defined.mk | 38 # Special characters that would be interpreted differently can be escaped.
93 # The :D and :U modifiers behave differently from the :@var@ modifier in
|
| H A D | varmod-match-escape.mk | 3 # As of 2020-08-01, the :M and :N modifiers interpret backslashes differently,
31 # comparison is parsed differently though. First, the expression
|
| H A D | sh-errctl.mk | 9 # line that behaves differently in these two modes is "false; true". In
|
| H A D | opt-define.mk | 30 # behaves differently, it defines a variable with the name 'VAR=value' and the
|
| H A D | varmod-ifelse.mk | 213 # parsed differently, depending on whether the branch was taken or not. When
240 # differently. The crucial difference is that the body of the modifier ':@'
302 # were parsed differently, depending on whether the branch was active or not.
|
| /freebsd/usr.sbin/mailwrapper/ |
| H A D | mailwrapper.8 | 90 The program knows to behave differently when its
188 .Dq behave differently if invoked with a different name
|
| /freebsd/sys/cddl/dev/dtrace/ |
| H A D | dtrace_cddl.h | 135 * Definitions for fields in struct proc which are named differently in FreeBSD.
141 * Definitions for fields in struct thread which are named differently in FreeBSD.
|
| /freebsd/crypto/openssl/ |
| H A D | NOTES-UNIX.md | 36 are talked about differently in their respective documentation;
115 differently, add `_a` suffix to link with them, e.g. `-lcrypto_a`.
|
| /freebsd/contrib/ntp/include/ |
| H A D | refclock_atom.h | 4 #undef NANOSECOND /* some systems define it differently */
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_CTX_set_split_send_fragment.pod | 63 Pipelining operates slightly differently for reading encrypted data compared to
85 apportioned differently. In the parallel case data will be spread equally
|
| /freebsd/contrib/tcpdump/ |
| H A D | print-nflog.c | 108 * correctly because some BSD systems define AF_INET6 differently from Linux
109 * (see af.h) and Haiku defines both AF_INET and AF_INET6 differently from
|
| /freebsd/tools/tools/editing/ |
| H A D | freebsd.el | 13 ;;; But emacs c-mode can't treat this differently from other multiple-line
|
| /freebsd/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/speculation/ |
| H A D | err.BufSizeVariations1.d | 39 * NOTES: This test behaves differently depending on the values
|
| H A D | err.BufSizeVariations2.d | 38 * NOTES: This test behaves differently depending on the values
|
| H A D | err.NegativeBufSize.d | 36 * NOTES: This test behaves differently depending on the values
|
| /freebsd/bin/sh/tests/expansion/ |
| H A D | cmdsubst2.0 | 25 # differently.
|
| /freebsd/lib/libc/posix1e/ |
| H A D | acl_set_tag_type.3 | 80 ACL is already branded differently.
|
| /freebsd/contrib/arm-optimized-routines/math/include/ |
| H A D | test_sig.h | 32 compile error). TEST_SIG is defined differently by various components of the
|
| /freebsd/contrib/tcsh/ |
| H A D | FAQ | 233 Why does FreeBSD's tcsh do history browsing differently than I expect?
240 differently if desired.
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | SSL_CTX_set_split_send_fragment.3 | 198 Pipelining operates slightly differently for reading encrypted data compared to
220 apportioned differently. In the parallel case data will be spread equally
|
| /freebsd/share/termcap/ |
| H A D | README | 36 there is a good reason not to, but I reserve the right to redo it differently.
|
| /freebsd/usr.sbin/memcontrol/ |
| H A D | memcontrol.8 | 50 cache to be programmed to behave differently depending on the region being
|