Home
last modified time | relevance | path

Searched refs:For (Results 1 – 25 of 2053) sorted by relevance

12345678910>>...83

/openbsd-src/usr.bin/make/
H A Dfor.h36 typedef struct For_ For; typedef
43 extern For *For_Eval(const char *);
47 extern bool For_Accumulate(For *, const char *);
52 extern void For_Run(For *);
H A Dfor.c130 For *
137 For *arg; in For_Eval()
211 For_Accumulate(For *arg, const char *line) in For_Accumulate()
250 For *arg = argp; in ForExec()
277 For_Run(For *arg) in For_Run()
/openbsd-src/gnu/llvm/llvm/include/llvm/IR/
H A DIntrinsicsRISCV.td161 // For unit stride mask load
170 // For unit stride load
180 // For unit stride fault-only-first load
193 // For unit stride load with mask
205 // For unit stride fault-only-first load with mask
219 // For strided load with passthru operand
229 // For strided load with mask
241 // For indexed load with passthru operand
251 // For indexed load with mask
263 // For unit stride store
[all …]
/openbsd-src/sys/arch/luna88k/conf/
H A DGENERIC.MP3 # For further information on compiling OpenBSD kernels, see the config(8)
6 # For further information on hardware support for this architecture, see
7 # the intro(4) man page. For further information about kernel options
8 # for this architecture, see the options(4) man page. For an explanation
H A DGENERIC3 # For further information on compiling OpenBSD kernels, see the config(8)
6 # For further information on hardware support for this architecture, see
7 # the intro(4) man page. For further information about kernel options
8 # for this architecture, see the options(4) man page. For an explanation
/openbsd-src/gnu/usr.bin/perl/vos/
H A DChanges4 For 5.8.9:
10 For 5.10.0:
15 For 5.9.0:
20 For 5.8.4:
24 For 5.8.0:
32 For the first time, full perl can now be built on VOS using
36 For 5.7.1:
47 For 5.7:
/openbsd-src/gnu/usr.bin/perl/lib/unicore/
H A DPropertyAliases.txt5 # For terms of use, see https://www.unicode.org/terms_of_use.html
8 # For documentation, see https://www.unicode.org/reports/tr44/
24 # For Unihan database tags, the short name is actually a longer string than
34 # values, the case distinctions, whitespace, and '_' are ignored. For Numeric Property
37 # NOTE: Property value names are NOT unique across properties. For example:
44 # For example:
51 # For more information, see UAX #44, Unicode Character Database, and
H A DReadMe.txt5 # For terms of use, see https://www.unicode.org/terms_of_use.html
7 # For documentation, see the following:
H A DNamedSqProv.txt4 # For terms of use, see https://www.unicode.org/terms_of_use.html
7 # For documentation, see https://www.unicode.org/reports/tr44/
31 # For more information, see UAX #34: Unicode Named Character
/openbsd-src/gnu/llvm/llvm/docs/
H A DOpaquePointers.rst8 Traditionally, LLVM IR pointer types have contained a pointee type. For example,
18 the pointer as. For example, a load needs to know how many bytes to load from
20 instructions themselves contain a type argument. For example the load
36 anything related to address spaces and lowering. For more information, see
142 the type of relevant operations instead. For example, memory access related
148 * For loads, use ``getType()``.
149 * For stores, use ``getValueOperand()->getType()``.
151 * For getelementptr instructions, use ``getSourceElementType()``.
152 * For calls, use ``getFunctionType()``.
153 * For allocas, use ``getAllocatedType()``.
[all …]
H A DNewPassManager.rst11 For an overview of the new pass manager, see the `blog post
50 For how to write a new PM pass, see :doc:`this page <WritingAnLLVMNewPMPass>`.
53 pass type and the pass manager type. For example, a ``FunctionPassManager``
100 A pass manager of a specific IR unit is also a pass of that kind. For
116 level pass manager. For example,
142 of optimization. For example, running all loop passes on a loop may cause a
155 pipeline. For example, frontends may want to add instrumentation, and target
156 backends may want to add passes that lower custom intrinsics. For these
158 certain parts of the pipeline. For example,
182 different ways of loading dynamic pass plugins. For example, ``opt
[all …]
H A DProjects.rst55 This subdirectory should contain all of your library source code. For each
70 automatically by the LLVM build system. For example, if you have a file
77 For each program that you build, you will have one directory in **tools**
119 directory of your project's source code. For example, if your source code
147 This variable contains the base name of the library that will be built. For
167 This variable contains the name of the program that will be built. For
176 ``lib`` prefix. For example, to link ``libsample.a``, you would set
185 libraries must be specified without their ``lib`` prefix. For example, to
201 the program. For example, to link with all LLVM libraries use
210 For example, to link ``libsample.so``, you would have the following line in
/openbsd-src/gnu/gcc/gcc/doc/include/
H A Dgcc-common.texi3 @c For copying conditions, see the file gcc.texi.
34 @c For FSF printing, define FSFPRINT. Also update the ISBN and last
55 @c Macro to generate a "For the N.N.N version" subtitle on the title
61 @subtitle For @sc{gcc} version @value{version-GCC}
64 @subtitle For @sc{gcc} version @value{version-GCC} (pre-release)
/openbsd-src/gnu/usr.bin/perl/
H A DChanges1 For an overview of what's changed in this release, see pod/perldelta.pod.
3 For the details of changes in previous releases, see the individual
4 perlNNNdelta.pod files. For example, pod/perl588delta.pod describes the
7 For a list of contributors to perl, see AUTHORS.
41 For example, the Changes5.005 file includes 206 spurious entries from the
/openbsd-src/gnu/usr.bin/gcc/gcc/doc/
H A Dservice.texi4 @c For copying conditions, see the file gcc.texi.
16 that brings no response, try @email{gcc@@gcc.gnu.org}. For help
27 For further information, see
H A Dgty.texi4 @c For copying conditions, see the file gcc.texi.
77 the array item currently being marked. For instance, if the field
135 value, and then specifying a discriminator using @code{desc}. For example,
168 For instance, to have a @code{htab_t} that points to trees, one should write
180 For this, @code{param1_is} through @code{param9_is} may be used to
277 For a back-end file, this is usually done
282 For files shared by all front ends, this is done by adding the
286 For any other file used by a front end, this is done by adding the
288 @file{config-lang.in}. For C, the file is @file{c-config-lang.in}.
291 list items. For example, it is common for front end writers to use
[all …]
/openbsd-src/gnu/gcc/gcc/doc/
H A Dservice.texi4 @c For copying conditions, see the file gcc.texi.
16 that brings no response, try @email{gcc@@gcc.gnu.org}. For help
27 For further information, see
H A Dgty.texi4 @c For copying conditions, see the file gcc.texi.
82 parameter entirely, or to provide an empty string as a parameter. For
103 For instance, suppose that you have a structure of the form
194 For example,
223 For instance, to have a @code{htab_t} that points to trees, one would
244 For this, @code{param1_is} through @code{param9_is} may be used to
316 @code{chain_prev} is an expression for the previous item. For singly
394 For a back-end file, this is usually done
399 For files shared by all front ends, add the filename to the
403 For files that are part of one front end, add the filename to the
[all …]
/openbsd-src/gnu/usr.bin/perl/dist/Devel-PPPort/parts/inc/
H A Dthreads26 For pre-5.6.0 thread compatibility, instead use dTHXR, available only through
36 For pre-5.6.0 thread compatibility, instead use aTHXR, available only through
42 For pre-5.6.0 thread compatibility, instead use aTHXR_, available only
/openbsd-src/etc/examples/
H A Dremote13 cua00|For i386,macppc:\
16 cuaa|For sparc:\
/openbsd-src/gnu/usr.bin/gcc/gcc/testsuite/
H A DREADME.gcc71 For tests that merely need to compile, put them in the "compile" directory.
73 For tests which should give an error, put them in the "noncompile" directory
76 For IEEE FP specific tests, put them in execute/ieee.
78 For execution tests, put them in execute.
/openbsd-src/gnu/llvm/libcxx/docs/DesignDocs/
H A DHeaderRemovalPolicy.rst10 headers. For example, instead of including ``<algorithm>`` entirely it is
13 aids reducing the growth of top-level headers. For example ``<atomic>`` uses
25 version of libc++. For example, ``<algorithm>`` is often forgotten but using
36 For libc++ developers, this means that any transitive include removal must be
/openbsd-src/gnu/llvm/llvm/utils/gn/secondary/third-party/unittest/
H A DBUILD.gn23 "googletest", # For including src/gtest.cc
24 "googlemock", # For including src/gmock.cc
/openbsd-src/gnu/usr.bin/perl/cpan/version/lib/version/
H A DInternals.pod14 For the purposes of this module, a version "number" is a sequence of
64 purposes of comparison with other version objects. For example:
112 For module authors using CPAN, the convention has been to note unstable
145 For dotted decimals:
159 For decimal versions:
181 For dotted-decimal versions, a leading 'v' is required, with three or
188 For decimal versions, an integer portion (no leading 0), a decimal point,
197 included in your own regular expressions freely. For example, consider
261 but other operations are not likely to be what you intend. For example:
278 leading 'v' character (also bare). For example:
[all …]
/openbsd-src/lib/libssl/test/
H A Dtest.cnf32 # For type CA, the listed attributes must be the same, and the optional
36 # For the CA policy
45 # For the 'anything' policy

12345678910>>...83