Searched refs:scenario (Results 1 – 25 of 41) sorted by relevance
12
| /openbsd/src/games/sail/ |
| D | globals.c | 35 struct scenario scene[] = {
304 int nscene = sizeof scene / sizeof (struct scenario);
549 struct scenario *cc; /* the current scenario */
|
| D | extern.h | 224 struct scenario { struct
232 extern struct scenario scene[]; argument
258 extern struct scenario *cc; /* the current scenario */
|
| /openbsd/src/usr.sbin/unbound/testcode/ |
| D | replay.h | 277 struct replay_scenario* scenario; member
|
| D | fake_event.c | 231 struct replay_range* p = runtime->scenario->range_list; in pending_find_match()
783 runtime->now = runtime->scenario->mom_first; in advance_moment()
885 runtime->now = runtime->scenario->mom_first; in run_scenario()
977 runtime->scenario = saved_scenario; in comm_base_create()
992 runtime->scenario= NULL; in comm_base_delete()
|
| /openbsd/src/gnu/llvm/clang/lib/CodeGen/ |
| D | README.txt | 32 performance, and in that scenario we will need to emit the alloca
|
| /openbsd/src/gnu/usr.bin/perl/pod/ |
| D | perl5283delta.pod | 54 usage scenario.
|
| D | perldbmfilter.pod | 68 For example, consider the following scenario. You have a DBM database
|
| D | perl5303delta.pod | 54 usage scenario.
|
| D | perlcall.pod | 343 This scenario will mostly be applicable to code that is meant to be called
1475 enclosing scope at some stage. In the event driven scenario that may
|
| D | perlembed.pod | 702 One way to avoid namespace collisions in this scenario is to translate
|
| /openbsd/src/regress/lib/libcrypto/certs/ |
| D | README | 3 that test a particular scenario. The root certificate(s) are contained
|
| /openbsd/src/gnu/llvm/clang/docs/ |
| D | LTOVisibility.rst | 122 in ``dso.so``. This is an example of the COM scenario; the definition of
|
| D | ClangTransformerTutorial.rst | 169 invocations. This scenario can arise, for example, if you want to collapse a
|
| /openbsd/src/gnu/gcc/gcc/doc/ |
| D | makefile.texi | 180 For example, in the aforementioned scenario of debugging a Fortran
|
| D | cfg.texi | 576 Another common scenario is redirection of branch instructions, but
|
| /openbsd/src/gnu/llvm/llvm/docs/ |
| D | AdvancedBuilds.rst | 79 bootstrapping scenario. Apple Clang is built using a 2-stage build.
|
| /openbsd/src/usr.bin/vi/cl/ |
| D | README.signal | 146 process group, not sent to a single process. The scenario goes something
|
| /openbsd/src/gnu/llvm/llvm/docs/Proposals/ |
| D | VectorizationPlan.rst | 27 VPlan-based vectorization involves three major steps, taking a "scenario-based
|
| /openbsd/src/gnu/lib/libstdc++/libstdc++/docs/html/ |
| D | abi.txt | 356 - what to do about multi-ABI systems (nathan scenario)?
|
| /openbsd/src/gnu/llvm/lldb/docs/use/ |
| D | variable.rst | 139 A frequent scenario is that your program has a typedef for a numeric type that
817 The above scenario works for Simple [3] as well as for any other array of
1120 As an example scenario, imagine we have a code generator that produces some
|
| /openbsd/src/usr.sbin/unbound/ |
| D | ax_pthread.m4 | 378 # linking. Such a scenario is extremely rare in practice.
|
| /openbsd/src/share/snmp/ |
| D | IANAifType-MIB.txt | 743 But in a DS-Lite scenario, the tunnel type is
|
| D | IP-FORWARD-MIB.txt | 263 scenario where no interface is specified."
|
| /openbsd/src/gnu/llvm/lldb/docs/resources/ |
| D | test.rst | 65 means that you have to have a well-defined test scenario that you can easily
|
| /openbsd/src/gnu/usr.bin/perl/dist/Locale-Maketext/lib/Locale/Maketext/ |
| D | TPJ13.pod | 649 scenario, but is worse than most. Most languages have simpler
|
12