HomeSort by: relevance | last modified time | path
    Searched refs:behavior (Results 1 - 25 of 25) sorted by relevancy

  /src/usr.bin/make/unit-tests/
make-exported.mk 5 # behavior for certain variable assignments.
12 # which was surprising behavior. Since 2020-10-03 this line tries to
counter-append.mk 8 # The cause for this surprising behavior was that the ::= variable modifiers
counter.mk 8 # The cause for this surprising behavior was that the ::= variable modifiers
varname-dot-make-save_dollars.mk 12 # behavior of the assignment operator ':=' depends. NetBSD's usr.bin/make
74 # does not restore the default behavior.
83 # does not restore the default behavior.
varmod-to-abs.mk 14 # This unintended behavior was caused by cached_realpath using a GNode for
varmod-match-escape.mk 8 # difference in behavior. When parsing the modifier text, only \{, \} and \:
77 # in behavior, or a proof that the behavior does not depend on the actual
cmdline.mk 49 # the behavior inconsistent.
directive-export.mk 13 # Before 2020-12-13, this unusual expression invoked undefined behavior since
directive-for-empty.mk 83 # the .for loops in a separate scope. To match the current behavior, there
103 # To emulate this exact behavior for the function 'empty', each file in the
120 # '::=', '::+=', '::?=', '::!=' and ':_' would lead to different behavior than
var-op-expand.mk 236 # silent unexpected behavior.
238 # As of 2021-11-20, the actual behavior is unexpected. Fixing it is not
267 # Due to all of this, this surprising behavior is not easy to fix.
varparse-undef-partial.mk 45 # It's difficult to decide what the best behavior is in this situation.
moderrs.mk 81 # Until 2020-11-01, the behavior in this case depended upon the size
85 # int (undefined behavior), typically resulting in -1. This -1 was
dep-var.mk 15 # feels like unintended behavior. At least the manual page says nothing at
var-scope-cmdline.mk 38 # overrides global". Due to an implementation mistake, the actual behavior
varmod-loop-varname.mk 114 # To make the behavior more predictable, the :@ modifier should restore the
escape.mk 23 # line immediately preceding an include line, the behavior is
varmod-edge.mk 6 # They may contain surprising behavior.
directive-for.mk 246 # corresponding .endfor. In other words, the behavior of the parser depends
var-scope-local.mk 110 # If the expression contains modifiers, the behavior depends on the
varmod-loop.mk 58 # To make the behavior more predictable, the :@ modifier should restore the
  /src/sys/secmodel/
secmodel.c 72 prop_dictionary_t behavior,
82 sm->sm_behavior = behavior;
137 * Adjust system-global secmodel behavior following the addition
188 /* Adjust behavior. */
218 /* Adjust behavior. */
  /src/sys/external/bsd/compiler_rt/dist/lib/sanitizer_common/
sanitizer_malloc_mac.inc 66 // This matches the behavior of malloc_create_zone() on OSX 10.7 and higher.
  /src/sys/dev/i2c/
dbcool.c 136 { "behavior", "operating behavior and temp selector",
723 static const char *behavior[] = { variable
1301 strlcpy(dbcool_cur_behav, behavior[reg], sizeof(dbcool_cur_behav));
1309 newreg = __arraycount(behavior);
1310 for (i = 0; i < __arraycount(behavior); i++)
1311 if (strcmp(node.sysctl_data, behavior[i]) == 0)
1313 if (i >= __arraycount(behavior))
1318 * ADM1030 splits fan controller behavior across two
  /src/sys/external/bsd/compiler_rt/dist/include/sanitizer/
linux_syscall_hooks.h 660 #define __sanitizer_syscall_pre_madvise(start, len, behavior) \
662 (long)(behavior))
663 #define __sanitizer_syscall_post_madvise(res, start, len, behavior) \
665 (long)(behavior))
2378 void __sanitizer_syscall_pre_impl_madvise(long start, long len, long behavior);
2380 long behavior);
  /src/share/mk/
bsd.own.mk 1458 # non-DYNAMICROOT behavior (i.e. it is only enabled for programs in /bin

Completed in 36 milliseconds