Home
last modified time | relevance | path

Searched refs:rules (Results 1 – 25 of 719) sorted by relevance

12345678910>>...29

/openbsd-src/gnu/usr.bin/perl/cpan/Test-Harness/t/
H A Dscheduler.t42 rules => $perl_rules,
47 rules => $perl_rules,
52 rules => $perl_rules,
61 rules => $incomplete_rules,
66 rules => $incomplete_rules,
71 rules => $incomplete_rules,
83 $test->{rules},
95 my $rules = {
115 rules => $rules
158 my $rules = { par => [ map { { seq => "$_*" } } 'A' .. 'Z' ] };
[all …]
H A Drulesfile.t50 is_deeply( $th->rules, $exp, "rules set from t/testrules.yml" );
71 is_deeply( $th->rules, $exp, "root testrules.yml overrides t/testrules.yml" );
90 is_deeply( $th->rules, $exp, "HARNESS_RULESFILE overrides testrules.yml" );
97 is_deeply( $th->rules, $exp, "rulesfile param overrides testrules.yml" );
/openbsd-src/regress/sys/net/pf_policy/
H A DMakefile59 .for rules in ${TESTS_PASS}
60 REGRESS_TARGETS += run-pass-${rules}
61 run-pass-${rules}:
63 ${SUDO} pfctl -a "regress" -f ${.CURDIR}/${rules}.conf
67 .for rules in ${TESTS_BLOCK}
68 REGRESS_TARGETS += run-block-${rules}
69 run-block-${rules}:
72 ${SUDO} pfctl -a "regress" -f ${.CURDIR}/${rules}.conf
76 .for rules in ${TESTS_ONCE}
77 REGRESS_TARGETS += run-once-${rules}
[all …]
/openbsd-src/share/zoneinfo/
H A Dziguard.awk177 rules = $rules_column
179 if (rules == "-") {
182 dstabbr_only = rules ~ /^[+0-9-]/
184 dstoff = get_minutes(rules)
187 if (rules == "Morocco" && NF == 3) {
189 } else if (rules == "NBorneo") {
191 } else if (((rules == "Cook" || rules == "LH") && NF == 3) \
192 || (rules == "Uruguay" \
195 } else if (rules
[all...]
/openbsd-src/sys/net/
H A Dpf_ruleset.c107 TAILQ_INIT(&ruleset->rules.queues[0]); in pf_init_ruleset()
108 TAILQ_INIT(&ruleset->rules.queues[1]); in pf_init_ruleset()
109 ruleset->rules.active.ptr = &ruleset->rules.queues[0]; in pf_init_ruleset()
110 ruleset->rules.inactive.ptr = &ruleset->rules.queues[1]; in pf_init_ruleset()
306 if (!TAILQ_EMPTY(ruleset->rules.active.ptr) || in pf_remove_if_empty_ruleset()
307 !TAILQ_EMPTY(ruleset->rules.inactive.ptr) || in pf_remove_if_empty_ruleset()
308 ruleset->rules.inactive.open) in pf_remove_if_empty_ruleset()
H A Dpf_ioctl.c153 * - rules,
560 while ((rule = TAILQ_FIRST(rs->rules.inactive.ptr)) != NULL) { in pf_begin_rules()
561 pf_rm_rule(rs->rules.inactive.ptr, rule); in pf_begin_rules()
562 rs->rules.inactive.rcount--; in pf_begin_rules()
564 *version = ++rs->rules.inactive.version; in pf_begin_rules()
565 rs->rules.inactive.open = 1; in pf_begin_rules()
576 if (rs == NULL || !rs->rules.inactive.open || in pf_rollback_rules()
577 rs->rules.inactive.version != version) in pf_rollback_rules()
579 while ((rule = TAILQ_FIRST(rs->rules.inactive.ptr)) != NULL) { in pf_rollback_rules()
580 pf_rm_rule(rs->rules in pf_rollback_rules()
[all...]
/openbsd-src/gnu/usr.bin/perl/cpan/Test-Harness/lib/TAP/Parser/
H A DScheduler.pm37 rules => \%rules,
40 Given 'tests' and optional 'rules' as input, returns a new
46 The optional C<rules> attribute provides direction on which tests should be run
53 The rules data structure is documented more in the next section.
57 The "C<rules>" data structure is the the heart of the scheduler. It allows you
58 to express simple rules like "run all tests in sequence" or "run all tests in
59 parallel except these five tests.". However, the rules structure also supports
105 =item * By default, all tests are eligible to be run in parallel. Specifying any of your own rules removes this one.
117 =head3 Glob-style pattern matching for rules
[all...]
/openbsd-src/usr.bin/doas/
H A Dparse.y50 struct rule **rules; variable
101 rules = reallocarray(rules, maxrules,
102 2 * sizeof(*rules));
103 if (!rules)
107 rules[nrules++] = r;
/openbsd-src/gnu/usr.bin/perl/cpan/Test-Harness/lib/App/
H A DProve.pm60 state_class test_args state dry extensions ignore_exit rules state_manager
85 argv rc_opts includes modules state plugins rules sources
246 'rules=s@' => $self->{rules},
371 if ( @{ $self->rules } ) {
372 my @rules;
373 for ( @{ $self->rules } ) {
375 push @rules, $1;
378 push @rules, { seq => $1 };
381 $args{rules}
[all...]
/openbsd-src/gnu/usr.bin/perl/dist/Devel-PPPort/
H A DMakefile.PL200 my @rules = split( m{^\s*$}m, $original );
202 foreach $rule ( @rules ) {
236 my @rules = split( m{^\s*$}m, $original );
238 foreach $rule ( @rules ) {
254 my @rules = split( m{^\s*$}m, $dist );
256 foreach $rule ( @rules ) {
/openbsd-src/gnu/llvm/llvm/cmake/platforms/
H A DClangClCMakeCompileRules.cmake3 # input file path to force it to be treated as a path. CMake's compilation rules
5 # CMake versions, overriding compilation rules works well enough. This file will
6 # be included by cmake after the default compilation rules have already been set
/openbsd-src/usr.bin/rsync/
H A Drules.c38 static struct rule *rules; variable
113 new = recallocarray(rules, rulesz, newsz, sizeof(*rules));
117 rules = new;
121 return rules + numrules - 1;
349 r = &rules[i];
422 r = &rules[i];
/openbsd-src/regress/usr.bin/make/
H A Dmk243 # .SUFFIXES should void suffixes rules
7 # Two suffixes implicit rules
H A Dmk268 # if there is no rules, we just silently accept the dependency
12 # if there is a set of rules, we transparently go through the dependencies
/openbsd-src/gnu/llvm/clang/docs/
H A DRefactoringEngine.rst32 operations (rules). These rules are grouped under a common umbrella - a single
33 ``clang-refactor`` command. In addition to rules, the refactoring action
57 grouped refactoring action rules that represent one refactoring operation.
58 Although the rules in one action may have a number of different implementations,
63 The distinction between actions and rules enables the creation of actions
64 that define a set of different rules that produce similar results. For example,
69 constant. To achieve that, we can create two different rules that will use one
81 Clang's refactoring engine supports several different refactoring rules:
136 rules for a particular action using the ``createRefactoringActionRule``
138 list of action rules using the following code:
[all …]
H A DClangTransformerTutorial.rst35 Transformer helps users succinctly specify rules of this sort and easily execute
77 ``makeRule`` is our go-to function for generating rewrite rules. It takes three
205 Reference: ranges, stencils, edits, rules
208 The above examples demonstrate just the basics of rewrite rules. Every element
210 and rules. In this section, we'll briefly review each in turn, with references
212 rewrite rules are actually rewriting.
218 explanation of what the rewrite rules are actually rewriting. We've referred to
329 We can also compose multiple *rules*, rather than just edits within a rule,
330 using ``applyFirst``: it composes a list of rules as an ordered choice, where
333 that case, ``applyFirst`` is simply joining the set of rules into one.
[all …]
/openbsd-src/usr.bin/yacc/
H A Dlr0.c380 rp2 = p->rules; in save_reductions()
400 short *rules; in set_derives() local
403 rules = NEW2(nvars + nrules, short); in set_derives()
407 derives[lhs] = rules + k; in set_derives()
410 rules[k] = i; in set_derives()
414 rules[k] = -1; in set_derives()
/openbsd-src/regress/sbin/pfctl/
H A Dpfail8.ok3 stdin:1: route-to, reply-to and dup-to are not supported on block rules
8 stdin:2: route-to, reply-to and dup-to are not supported on block rules
/openbsd-src/gnu/usr.bin/perl/cpan/Test-Harness/lib/TAP/
H A DHarness.pm83 rules => sub { shift; shift },
326 can be run in parallel is controlled by C<rules>. The default is to
329 =item * C<rules>
331 A reference to a hash of rules that control which tests may be executed in
332 parallel. If no rules are declared and L<CPAN::Meta::YAML> is available,
333 C<TAP::Harness> attempts to load rules from a YAML file specified by the
334 C<rulesfile> parameter. If no rules file exists, the default is for all
342 $harness->rules({
351 $harness->rules({
366 $harness->rules({
[all...]
/openbsd-src/gnu/usr.bin/perl/
H A Dregcomp.sym75 BOUNDU BOUND, no ; Match "" at any boundary of a given type using /u rules.
80 …UNDU NBOUND, no ; Match "" at any non-boundary of a given type using using /u rules.
157 EXACTF EXACT, str ; Like EXACT, but match using /id rules; (string not UTF-8, ASCII…
158 EXACTFL EXACT, str ; Like EXACT, but match using /il rules; (string not likely to be…
159 EXACTFU EXACT, str ; Like EXACT, but match using /iu rules; (string folded)
165 EXACTFAA EXACT, str ; Like EXACT, but match using /iaa rules; (string folded except MICRO…
171 EXACTFUP EXACT, str ; Like EXACT, but match using /iu rules; (string not UTF-8, folded ex…
185 EXACTFU_S_EDGE EXACT, str ; /di rules, but nothing in it precludes /ui, except begins and/o…
237 REFF REF, num 2 V ; Match already matched string, using /di rules.
238 REFFL REF, num 2 V ; Match already matched string, using /li rules.
[all …]
/openbsd-src/usr.sbin/zic/
H A Dzic.c256 static struct rule *rules;
257 static int nrules; /* number of rules */
666 ** Associate sets of rules with zones.
688 qsort(rules, nrules, sizeof *rules, rcomp); in associate()
690 if (strcmp(rules[i].r_name, in associate()
691 rules[i + 1].r_name) != 0) in associate()
693 if (strcmp(rules[i].r_filename, in associate()
694 rules[i + 1].r_filename) == 0) in associate()
696 eat(rules[ in associate()
252 static struct rule *rules; global() variable
[all...]
/openbsd-src/usr.sbin/bgpd/
H A Drde_peer.c81 peer_init(struct filter_head *rules) in peer_shutdown()
89 peerself = peer_add(PEER_ID_SELF, &pc, rules);
157 peer_add(uint32_t id, struct peer_config *p_conf, struct filter_head *rules) in peer_add()
183 peer_apply_out_filter(peer, rules); in peer_add()
209 peer_apply_out_filter(struct rde_peer *peer, struct filter_head *rules) in peer_apply_out_filter()
219 TAILQ_FOREACH(fr, rules, entry) { in peer_cmp()
66 peer_init(struct filter_head * rules) peer_init() argument
136 peer_add(uint32_t id,struct peer_config * p_conf,struct filter_head * rules) peer_add() argument
188 peer_apply_out_filter(struct rde_peer * peer,struct filter_head * rules) peer_apply_out_filter() argument
/openbsd-src/gnu/usr.bin/perl/t/
H A Dharness109 my ($rules, $state, $color);
278 # Now construct the rules. Each of the parallel tests is made into a
295 # Generate T::H schedule rules that run the contents of each directory
325 # Ideally we'd get somewhere close to Tux's Oslo rules
326 # my $rules = {
370 $rules = { seq => \@seq };
379 "directory scanning rules. You should update t/harness line 339 or so.\n",
431 rules => $rules,
/openbsd-src/gnu/llvm/llvm/utils/vim/
H A DREADME4 tablegen *.td files. It comes with filetype detection rules in the (ftdetect),
17 highlighting (because the files have names such as Makefile.rules or
/openbsd-src/gnu/llvm/llvm/docs/GlobalISel/
H A DLegalizer.rst70 and describes a set of rules by which we can either declare an instruction legal
104 opcode(s) that rules can be added to. If multiple opcodes are given, they are
105 all permanently bound to the same ruleset. The rules in a ruleset are executed
107 legalized as a result of the rules. If the ruleset is exhausted without
110 When it doesn't declare the instruction legal, each pass over the rules may
118 the rule as possible and to place any expensive rules as low as possible. This
120 legalization and legalization can require multiple passes over the rules.
151 There are various rule factories that append rules to a ruleset but they have a
234 There are some composite rules for common situations built out of the above facilities:
330 There are no minimum rules for pointers since G_INTTOPTR and G_PTRTOINT can
[all …]

12345678910>>...29