| /freebsd/contrib/one-true-awk/testdir/ |
| H A D | bib | 14 … in the firmament of the heaven to divide the day from the night; and let them be for signs, and f…
15 And let them be for lights in the firmament of the heaven to give light upon the earth: and it was …
17 And God set them in the firmament of the heaven to give light upon the earth,
22 And God blessed them, saying, Be fruitful, and multiply, and fill the waters in the seas, and let f…
26 And God said, Let us make man in our image, after our likeness: and let them have dominion over the…
27 … created man in his own image, in the image of God created he him; male and female created he them.
28 And God blessed them, and God said unto them, Be fruitful, and multiply, and replenish the earth, a…
32 Thus the heavens and the earth were finished, and all the host of them.
50 … of the field, and every fowl of the air; and brought them unto Adam to see what he would call the…
63 And the eyes of them both were opened, and they knew that they were naked; and they sewed fig leave…
[all …]
|
| /freebsd/contrib/llvm-project/clang/lib/Driver/ToolChains/ |
| H A D | Flang.h | 27 /// Extract fortran dialect options from the driver arguments and add them to
35 /// Extract preprocessing options from the driver arguments and add them to
43 /// Extract PIC options from the driver arguments and add them to
51 /// Extract target options from the driver arguments and add them to
87 /// Extract offload options from the driver arguments and add them to
98 /// Extract options for code generation from the driver arguments and add them
106 /// Extract other compilation options from the driver arguments and add them
|
| /freebsd/share/doc/papers/malloc/ |
| H A D | kernel.ms | 23 how the kernels exploited them varied a lot from UNIX to UNIX and from
29 consequently just as writable as them.
39 pages out to free them up, and then plugs them into the page-table of
46 the rest will be paged in, if and when the process tries to access them.
|
| /freebsd/contrib/googletest/googletest/samples/ |
| H A D | sample7_unittest.cc | 46 // instead of reusing them. In this sample we will define a simple factory
48 // SetUp() method and delete them in TearDown() method.
102 // In order to run value-parameterized tests, you need to instantiate them,
103 // or bind them to a list of values which will be used as test parameters.
104 // You can instantiate them in a different translation module, or even
105 // instantiate them several times.
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/Support/ |
| H A D | TargetSelect.h | 10 // linked into the main application executable, and initialize them as
53 /// support, to make them available via the TargetRegistry.
63 /// support, to make them available via the TargetRegistry.
76 /// support, to make them available via the TargetRegistry.
85 /// it wants all asm printers that LLVM is configured to support, to make them
95 /// wants all asm parsers that LLVM is configured to support, to make them
106 /// them available via the TargetRegistry.
|
| /freebsd/contrib/llvm-project/lld/docs/ |
| H A D | NewLLD.rst | 14 files in the usual way and give them to the linker. It is naturally expected to
53 until we need them to continue linking.
132 and inserting all of them to a hash table takes 1.5 seconds.
143 be understood as the interactions between them. Once you understand their
194 and how to apply relocations to them.
196 and how to apply them.
224 a file. It creates OutputSections, put all InputSections/Chunks into them,
225 assign unique, non-overlapping addresses and file offsets to them, and then
226 write them down to a file.
246 with all bitcode files to convert them to one big regular ELF/COFF file.
|
| /freebsd/lib/libc/db/hash/ |
| H A D | README | 5 All test programs which need key/data pairs expect them entered
32 Reads the key/data pairs in the file hashtest and writes them
37 Reads key/data pairs from standard in and looks them up
40 Reads key/data pairs from standard in, looks them up
|
| /freebsd/contrib/jemalloc/src/ |
| H A D | test_hooks.c | 5 * sense that we want them available to end-users, but we do want them visible
6 * from outside the generated library, so that we can use them in test code.
|
| /freebsd/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/funcs/ |
| H A D | tst.substr.d.out | 236 if (substr("CRAIG: Positioned them, I don't know... I'm fairly wide guy.", 100, 10) ne "") {
237 …printf("perl => substr(\"CRAIG: Positioned them, I don't know... I'm fairly wide guy.\", 100, 10) …
238 substr("CRAIG: Positioned them, I don't know... I'm fairly wide guy.", 100, 10));
239 …printf(" D => substr(\"CRAIG: Positioned them, I don't know... I'm fairly wide guy.\", 100, 10) …
244 if (substr("CRAIG: Positioned them, I don't know... I'm fairly wide guy.", 100) ne "") {
245 …printf("perl => substr(\"CRAIG: Positioned them, I don't know... I'm fairly wide guy.\", 100) = \"…
246 substr("CRAIG: Positioned them, I don't know... I'm fairly wide guy.", 100));
247 …printf(" D => substr(\"CRAIG: Positioned them, I don't know... I'm fairly wide guy.\", 100) = \"…
|
| /freebsd/contrib/libpcap/pcap/ |
| H A D | sll.h | 68 * handle DLT_LINUX_SLL captures will continue to handle them correctly
70 * can be told apart and programs that read them can dissect the
71 * packets in them.
113 * define them here so that they're available even on systems other
129 * if we don't translate them in "pcap-linux.c", capture files
133 * if we do translate them in "pcap-linux.c", that makes life
|
| /freebsd/share/doc/psd/04.uprog/ |
| H A D | p2 | 89 and loops until it has printed them all.
94 If you want to keep them around so other
95 routines can get at them, you must
96 copy them to external variables.
209 so calls to them may also be intermixed.
|
| /freebsd/share/doc/usd/07.mail/ |
| H A D | mail2.nr | 108 next to them in the header listing and old, but unread messages have
111 next to them.
301 you type them, either. The effect is to make the message disappear
367 print long messages, they fly by too quickly for you to read them.
401 for them, you would use the
429 To make them more convenient to use,
495 to read them with:
548 command to have them so saved. For example,
577 that you will see them the next time you type:
|
| /freebsd/contrib/libpcap/doc/ |
| H A D | README.macos | 26 Both of them will change the ownership of the BPF devices so that the
27 "admin" group owns them, and will change the permission of the BPF
30 both read and write access to them.
63 access them, you can have the ChmodBPF/ChmodBPF script change the
|
| /freebsd/sys/dev/isp/ |
| H A D | Hardware.txt | 60 to the role you're using them for- otherwise things don't
150 can see them very clearly from 50 feet away.
187 typically have had few problems with them. These are the bare
198 on the JBOD you put them to carry this dual port to the outside
273 want them to- and this makes for a much more reliable, if more expensive,
298 fabric login policy is simplistic (log them in as you find them). If
|
| /freebsd/sbin/ipf/ipf/ |
| H A D | ipfilter.4 | 93 reads in a set of rules, from either stdin or a file, and adds them to
94 the kernels current list (appending them). It can also be used to flush the
100 and NAT mappings) and write them to disk. After that the system can be
102 them into the kernel. This way the system can be rebooted without the
138 reads in a set of rules, from either stdin or a file and adds them
|
| /freebsd/tools/tools/locale/ |
| H A D | README | 14 "make" downloads the necessary files, build them, and install the
35 them and they are not changed as long as using the same
44 If something is missing, install them.
|
| /freebsd/usr.bin/at/ |
| H A D | privs.h | 35 * with the option of getting them back later. This is done by
45 * and the effective group id to b, with the option to get them back
59 * can acquire them just as easily. Set both effective and real userid
60 * to the real userid before calling any of them.
|
| /freebsd/contrib/llvm-project/llvm/utils/TableGen/Common/GlobalISel/ |
| H A D | CombinerUtils.h | 23 /// DagInit's support any type inside them.
34 /// DagInit's since DagInit's support any type inside them.
45 /// DagInit's support any type inside them.
59 /// similar in DagInit's since DagInit's support any type inside them.
|
| /freebsd/contrib/llvm-project/clang/include/clang/Basic/ |
| H A D | TokenKinds.def | 880 // handles them.
885 // handles them.
890 // handles them.
895 // handles them.
905 // handles them.
910 // handles them.
915 // handles them.
920 // handles them.
925 // handles them.
930 // handles them.
[all …]
|
| /freebsd/contrib/ldns/ldns/ |
| H A D | dnssec_sign.h | 136 * added to this rr list, so the caller can free them later
178 * added to this list, so the caller can free them
203 * added to this list, so the caller can free them
222 * \param[in] new_rrs newly created resource records are added to this list, to free them later
254 * \param[in] new_rrs newly created resource records are added to this list, to free them later
282 * \param[in] new_rrs newly created resource records are added to this list, to free them later
316 * \param[in] new_rrs newly created resource records are added to this list, to free them later
342 * \param[in] new_rrs newly created resource records are added to this list, to free them later
|
| /freebsd/crypto/heimdal/lib/roken/ |
| H A D | missing | 65 to install the \`Automake' and \`Perl' packages. Grab them from
74 \`Autoconf' and \`GNU m4' packages. Grab them from any GNU
83 to install the \`Autoconf' and \`GNU m4' packages. Grab them
103 Grab them from any GNU archive site."
182 proper tools for further handling them. Check the \`README' file,
|
| /freebsd/contrib/libpcap/ |
| H A D | pcap-common.c | 95 * making them collide with any of the LINKTYPE_*
275 * tcpdump release use them, either.
279 * particular, do *NOT* use them in products, otherwise you may find that
284 * not accept patches to let them read those files.
286 * Also, do not use them if somebody might send you a capture using them
287 * for *their* private type and tools using them for *your* private type
288 * would have to read them.
1021 * So I'll just give them one; hopefully this will show up in a
1022 * libpcap release in time for them to get this into 10.10 Big Sur
1276 * platforms, so we assigned them LINKTYPE_* codes just in dlt_to_linktype()
[all …]
|
| /freebsd/contrib/llvm-project/llvm/lib/Support/Unix/ |
| H A D | DynamicLibrary.inc | 76 // If this is darwin, it has some funky issues, try to solve them here. Some
78 // SearchForAddressOfSymbol to find them. As such, we special case them here,
79 // there is only a small handful of them.
|
| /freebsd/contrib/ntp/sntp/libevent/ |
| H A D | whatsnew-2.0.txt | 55 historically exposed. Exposing them caused problems in the past,
58 layout of some object. We've moving them into separate headers so
88 the caller needed to explicitly reattach them to another base.
99 for them. But since the size and contents of struct event can
134 issues, or so on), you can replace them by calling
230 implement mutexes, conditions, and thread IDs, and passing them to
270 re-initialize them, or otherwise put Libevent in an internally inconsistent
441 and you want to avoid having them recurse and overflow your stack.
514 bufferevent, or by a group of them, you can do this with a new set of
553 argument. This makes them easier to wrap for other (more OO) languages,
[all …]
|
| /freebsd/contrib/libevent/ |
| H A D | whatsnew-2.0.txt | 55 historically exposed. Exposing them caused problems in the past,
58 layout of some object. We've moving them into separate headers so
88 the caller needed to explicitly reattach them to another base.
99 for them. But since the size and contents of struct event can
134 issues, or so on), you can replace them by calling
230 implement mutexes, conditions, and thread IDs, and passing them to
270 re-initialize them, or otherwise put Libevent in an internally inconsistent
441 and you want to avoid having them recurse and overflow your stack.
514 bufferevent, or by a group of them, you can do this with a new set of
553 argument. This makes them easier to wrap for other (more OO) languages,
[all …]
|