| /openbsd/src/gnu/usr.bin/perl/ |
| D | .metaconf-exclusions.txt | 4 # relevant probe. But in some cases, that's inappropriate: we have symbols that
12 # us to maintain those customised units for as long as the relevant symbols are
17 # will prevent the relevant units from being used.
20 # to be included, even before specific code using the relevant symbols has been
|
| D | PACKAGING | 24 enforce rules which are not relevant to downstream packagers. These can
|
| /openbsd/src/gnu/llvm/lldb/cmake/modules/ |
| D | debugserverConfig.cmake | 1 # Duplicate options from LLDBConfig that are relevant for debugserver Standalone builds.
|
| /openbsd/src/gnu/usr.bin/perl/cpan/Test-Simple/t/Legacy/Regression/ |
| D | is_capture.t | 5 # this test is only relevant under Devel::Cover
|
| /openbsd/src/gnu/llvm/clang/include/clang/Basic/ |
| D | TargetCXXABI.def | 80 /// The relevant changes from the generic ABI in this case are:
108 /// The relevant changes from the Itanium ABI are:
115 /// The relevant changes from the Itanium ABI are:
|
| /openbsd/src/gnu/gcc/gcc/ |
| D | tree-vectorizer.h | 188 bool relevant; member
235 #define STMT_VINFO_RELEVANT_P(S) (S)->relevant
|
| D | tree-ssa-loop-ivopts.c | 219 bitmap relevant; member
820 data->relevant = BITMAP_ALLOC (NULL); in tree_ssa_iv_optimize_init()
917 bitmap_set_bit (data->relevant, SSA_NAME_VERSION (iv)); in set_iv()
1124 EXECUTE_IF_SET_IN_BITMAP (data->relevant, 0, i, bi) in find_induction_variables()
1185 bitmap_set_bit (data->relevant, SSA_NAME_VERSION (op)); in record_invariant()
1765 EXECUTE_IF_SET_IN_BITMAP (data->relevant, 0, i, bi) in find_interesting_uses()
2180 EXECUTE_IF_SET_IN_BITMAP (data->relevant, 0, i, bi) in add_old_ivs_candidates()
4460 EXECUTE_IF_SET_IN_BITMAP (data->relevant, 0, j, bi) in determine_set_costs()
5702 EXECUTE_IF_SET_IN_BITMAP (data->relevant, 0, j, bi) in remove_unused_ivs()
5727 EXECUTE_IF_SET_IN_BITMAP (data->relevant, 0, i, bi) in free_loop_data()
[all …]
|
| /openbsd/src/gnu/llvm/clang/ |
| D | README.txt | 14 the relevant web sites. Here are some pointers:
|
| /openbsd/src/usr.sbin/pkg_add/OpenBSD/ |
| D | State.pod | 27 As such, it contains internal state elements relevant to the working of
59 handle options to relevant to this command. Takes a C<OpenBSD::Getopt>
|
| /openbsd/src/gnu/usr.bin/gcc/gcc/config/sparc/ |
| D | sparc-modes.def | 30 We also have two modes to indicate that the relevant condition code is
|
| /openbsd/src/distrib/notes/i386/ |
| D | xfer | 29 refer to the relevant man pages or administrator's guide for the
|
| /openbsd/src/gnu/gcc/gcc/config/sparc/ |
| D | sparc-modes.def | 33 We also have two modes to indicate that the relevant condition code is
|
| /openbsd/src/distrib/notes/amd64/ |
| D | xfer | 29 refer to the relevant man pages or administrator's guide for the
|
| /openbsd/src/gnu/lib/libstdc++/libstdc++/testsuite/ |
| D | README | 7 correlated to the relevant chapters in the standard. For example, the
36 Inside a test file, the plan is to test the relevant parts of the
41 after the relevant (and more specific) part of the standard.
|
| /openbsd/src/gnu/usr.bin/binutils/gdb/ |
| D | CONTRIBUTE | 49 taking care of your contributions) to obtain the relevant
92 o Please try to run the relevant testsuite before and after
|
| /openbsd/src/gnu/llvm/clang/docs/ |
| D | RAVFrontendAction.rst | 61 RecursiveASTVisitor to extract the relevant information from the AST.
66 for the relevant node types.
|
| /openbsd/src/gnu/usr.bin/perl/lib/unicore/ |
| D | NormalizationCorrections.txt | 14 # for any character, once established in a relevant version
|
| /openbsd/src/gnu/llvm/llvm/lib/Target/WebAssembly/ |
| D | WebAssembly.td | 103 // consideration given to available support in relevant engines and tools, and
|
| /openbsd/src/gnu/llvm/llvm/docs/ |
| D | Packaging.rst | 27 versions of LLVM in parallel. The following configure flags are relevant:
|
| D | RISCVUsage.rst | 42 ratified and thus have finalized specifications. When relevant, detailed notes
111 …ompiler. This includes everything in Assembly Support, along with - if relevant - C language intr…
|
| D | HowToUseInstrMappings.rst | 17 added in the .td files, all the relevant switch cases should be modified
115 to include relevant information in its definition. For example, consider
|
| /openbsd/src/gnu/usr.bin/perl/Porting/ |
| D | how_to_write_a_perldelta.pod | 186 C<_PERLLIB>, but it's a start. Where relevant, a summary of changes can be
190 the changelogs for dual lived modules. For each of them, grab the relevant
194 (And if not, experiment with using F<git> to get the relevant part of changelog
|
| /openbsd/src/gnu/llvm/libcxx/docs/ |
| D | Contributing.rst | 35 - Did you update the synopsis of the relevant headers?
36 - Did you update the relevant files to track implementation status (in ``docs/Status/``)?
45 - Did you add the relevant feature test macro(s) for your feature? Did you update the ``generate_fe…
|
| /openbsd/src/gnu/usr.bin/perl/dist/threads-shared/t/ |
| D | waithires.t | 180 # relevant interval exceeded the timeout
315 # relevant interval exceeded the timeout
|
| /openbsd/src/gnu/lib/libreadline/doc/ |
| D | rluserman.texinfo | 30 (this paragraph not being relevant to the printed manual).
|