| /openbsd-src/usr.bin/calendar/calendars/ |
| H A D | calendar.discord | 10 01/01 Sweetmorn, day 1 in the season of Chaos, 3172.
11 01/02 Boomtime, day 2 in the season of Chaos, 3172.
12 01/03 Pungenday, day 3 in the season of Chaos, 3172.
13 01/04 Prickle-Prickle, day 4 in the season of Chaos, 3172.
14 01/05 Setting Orange, day 5 in the season of Chaos, 3172.
15 It is the sacred Apostle Holyday of Mungday.
16 01/06 Sweetmorn, day 6 in the season of Chaos, 3172.
17 01/07 Boomtime, day 7 in the season of Chaos, 3172.
18 01/08 Pungenday, day 8 in the season of Chaos, 3172.
19 01/09 Prickle-Prickle, day 9 in the season of Chaos, 3172.
[all …]
|
| /openbsd-src/usr.bin/vi/docs/tutorial/ |
| H A D | vi.beginner | 8 uses the vi editor itself as the means of presentation.
11 the indicated actions. This tutorial (or, at least, the first half of it) has
12 been designed to systematically present the vi commands IF THE INSTRUCTIONS
14 you ever find yourself stuck, remember the first line of this section.
16 OK, now find the control key on your keyboard; it usually has CTL or CTRL
17 written on its upper surface. Your first assignment is to hold the control
18 key down while you press the 'F' key on your keyboard. Please do so now.
23 Many of vi's commands use the control key and some other key in combination,
24 as with the control and the 'F' key above. This is abbreviated CTL-F, or ^F.
27 number of lines in the file. Throughout the remainder of the tutorial when
[all …]
|
| H A D | vi.advanced | 1 Section 26: Index to the rest of the tutorial
3 The remainder of the tutorial can be perused at your leisure. Simply find the
4 topic of interest in the following list, and {/Section xx:/^M} to get to the
5 appropriate section. (Remember that ^M means the return key)
7 The material in the following sections is not necessarily in a bottom up
10 several {n} to do a keyword search of the file for more details on that item.
12 can therefore be found rather easily. To see where, say, the X command is
13 used try {/{X}/^M}. Subsequent {n} will show you other places the command was
14 used. We have tried to maintain the convention of placing the command letter
15 surrounded by curly-braces on the section line where that command is
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils-2.17/gprof/ |
| H A D | fsf_callg_bl.m | 2 This table describes the call tree of the program, and was sorted by
3 the total amount of time spent in each function and its children.
5 Each entry in this table consists of several lines. The line with the
6 index number at the left hand margin lists the current function.
7 The lines above it list the functions that called this function,
8 and the lines below it list the functions this one called.
10 index A unique number given to each element of the table.
13 it is easier to look up where the function in the table.
15 % time This is the percentage of the `total' time that was spent
20 self This is the total amount of time spent in this function.
[all …]
|
| H A D | bsd_callg_bl.m | 5 The sum of self and descendents is the major sort
10 index the index of the function in the call graph
13 %time the percentage of the total time of the program
17 self the number of seconds spent in this function
21 the number of seconds spent in the descendents of
24 called the number of times this function is called (other
27 self the number of times this function calls itself
30 name the name of the function, with an indication of
33 index the index of the function in the call graph
40 self* the number of seconds of this function's self time
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils/gprof/ |
| H A D | fsf_callg_bl.m | 2 This table describes the call tree of the program, and was sorted by
3 the total amount of time spent in each function and its children.
5 Each entry in this table consists of several lines. The line with the
6 index number at the left hand margin lists the current function.
7 The lines above it list the functions that called this function,
8 and the lines below it list the functions this one called.
10 index A unique number given to each element of the table.
13 it is easier to look up where the function in the table.
15 % time This is the percentage of the `total' time that was spent
20 self This is the total amount of time spent in this function.
[all …]
|
| H A D | bsd_callg_bl.m | 5 The sum of self and descendents is the major sort
10 index the index of the function in the call graph
13 %time the percentage of the total time of the program
17 self the number of seconds spent in this function
21 the number of seconds spent in the descendents of
24 called the number of times this function is called (other
27 self the number of times this function calls itself
30 name the name of the function, with an indication of
33 index the index of the function in the call graph
40 self* the number of seconds of this function's self time
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils-2.17/bfd/doc/ |
| H A D | linker.texi | 3 The linker uses three special entry points in the BFD target
10 The first routine creates a hash table used by the other
11 routines. The second routine adds the symbols from an object
12 file to the hash table. The third routine takes all the
13 object files and links them together to create the output
14 file. These routines are designed so that the linker proper
15 does not need to know anything about the symbols in the object
16 files that it is linking. The linker merely arranges the
17 sections as directed by the linker script and lets BFD handle
18 the details of symbols and relocs.
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils/bfd/doc/ |
| H A D | linker.texi | 3 The linker uses three special entry points in the BFD target
10 The first routine creates a hash table used by the other
11 routines. The second routine adds the symbols from an object
12 file to the hash table. The third routine takes all the
13 object files and links them together to create the output
14 file. These routines are designed so that the linker proper
15 does not need to know anything about the symbols in the object
16 files that it is linking. The linker merely arranges the
17 sections as directed by the linker script and lets BFD handle
18 the details of symbols and relocs.
[all …]
|
| /openbsd-src/gnu/llvm/llvm/bindings/ocaml/llvm/ |
| H A D | llvm.mli | 3 * Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
11 This interface provides an OCaml API for the LLVM intermediate
12 representation, the classes in the VMCore library. *)
17 These abstract types correlate directly to the LLVMCore classes. *)
19 (** The top-level container for all LLVM global data. See the
24 objects. See the [llvm::Module] class. *)
27 (** Opaque representation of Metadata nodes. See the [llvm::Metadata] class. *)
30 (** Each value in the LLVM IR has a type, an instance of [lltype]. See the
34 (** Any value in the LLVM IR. Functions, instructions, global variables,
35 constants, and much more are all [llvalues]. See the [llvm::Value] class.
[all …]
|
| /openbsd-src/regress/usr.bin/dc/ |
| H A D | t3.out | 1 99 bottles of beer on the wall, 99 bottles of beer,
3 98 bottles of beer on the wall.
4 98 bottles of beer on the wall, 98 bottles of beer,
6 97 bottles of beer on the wall.
7 97 bottles of beer on the wall, 97 bottles of beer,
9 96 bottles of beer on the wall.
10 96 bottles of beer on the wall, 96 bottles of beer,
12 95 bottles of beer on the wall.
13 95 bottles of beer on the wall, 95 bottles of beer,
15 94 bottles of beer on the wall.
[all …]
|
| /openbsd-src/gnu/llvm/lldb/docs/ |
| H A D | doxygen.cfg.in | 3 # This file describes the settings to be used by the documentation system
17 # This tag specifies the encoding used for all characters in the config file
18 # that follow. The default is UTF-8 which is also the encoding used for all
19 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
20 # iconv built into libc) for the transcoding. See
21 # http://www.gnu.org/software/libiconv for the list of possible encodings.
26 # by quotes) that should identify the project.
31 # This could be handy for archiving the generated documentation or
36 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
37 # base path where the generated documentation will be put.
[all …]
|
| /openbsd-src/gnu/llvm/clang/docs/ |
| H A D | PCHInternals.rst | 8 This document describes the design and implementation of Clang's precompiled
9 headers (PCH) and modules. If you are interested in the end-user view, please
10 see the :ref:`User's Manual <usersmanual-precompiled-headers>`.
18 To generate PCH files using ``clang -cc1``, use the option `-emit-pch`:
25 resulting PCH file contains the serialized form of the compiler's internal
27 file can then be used as a prefix header with the `-include-pch`
38 the design of precompiled headers is entirely driven by performance concerns.
40 common set of headers that is included in nearly every source file in the
42 header (PCH file). Then, when compiling the source files in the project, we
43 load the PCH file first (as a prefix header), which acts as a stand-in for that
[all …]
|
| H A D | OffloadingDesign.rst | 11 This document describes the Clang driver and code generation steps for creating
14 document is to illustrate the steps necessary to create an offloading
22 Clang and then executed using the ``libomptarget`` runtime and the associated
23 plugin for the target architecture, e.g. ``libomptarget.rtl.cuda``. This section
24 describes the steps necessary to create a functioning device image that can be
25 loaded by the OpenMP runtime. More information on the OpenMP runtimes can be
26 found at the `OpenMP documentation page <https://openmp.llvm.org>`__.
34 can be run on the target device. OpenMP offloading creates executable images by
35 compiling the input file for both the host and the target device. The output
36 from the device phase then needs to be embedded into the host to create a fat
[all …]
|
| /openbsd-src/gnu/lib/libreadline/doc/ |
| H A D | hsuser.texinfo | 2 This file documents the user interface to the GNU History library.
8 provided the copyright notice and this permission notice are preserved on
11 Permission is granted to process this file through Tex and print the
12 results, provided the printed document carries copying permission notice
13 identical to this one except for the removal of this paragraph (this
14 paragraph not being relevant to the printed manual).
17 manual under the conditions for verbatim copying, provided also that the
18 GNU Copyright statement is available to the distributee, and provided that
19 the entire resulting derived work is distributed under the terms of a
23 into another language, under the above conditions for modified versions.
[all …]
|
| /openbsd-src/gnu/lib/libstdc++/libstdc++/docs/doxygen/ |
| H A D | user.cfg.in | 3 # This file describes the settings to be used by the documentation system
13 ### When doxygen is run, the current directory is the top of the
25 # by quotes) that should identify the project.
30 # This could be handy for archiving the generated documentation or
35 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
36 # base path where the generated documentation will be put.
37 # If a relative path is entered, it will be relative to the location
38 # where doxygen was started. If left blank the current directory will be used.
42 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
44 # information to generate all constant output in the proper language.
[all …]
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/config/c4x/ |
| H A D | c4x-modes.def | 10 it under the terms of the GNU General Public License as published by
11 the Free Software Foundation; either version 2, or (at your option)
14 GNU CC is distributed in the hope that it will be useful,
15 but WITHOUT ANY WARRANTY; without even the implied warranty of
16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
19 You should have received a copy of the GNU General Public License
20 along with GNU CC; see the file COPYING. If not, write to
21 the Free Software Foundation, 59 Temple Place - Suite 330,
24 /* Add any extra modes needed to represent the condition code.
26 On the C4x, we have a "no-overflow" mode which is used when an ADD,
[all …]
|
| /openbsd-src/gnu/usr.bin/binutils/gdb/doc/ |
| H A D | inc-hist.texinfo | 2 This file documents the user interface to the GNU History library.
8 provided the copyright notice and this permission notice are preserved on
11 Permission is granted to process this file through Tex and print the
12 results, provided the printed document carries copying permission notice
13 identical to this one except for the removal of this paragraph (this
14 paragraph not being relevant to the printed manual).
17 manual under the conditions for verbatim copying, provided also that the
18 GNU Copyright statement is available to the distributee, and provided that
19 the entire resulting derived work is distributed under the terms of a
23 into another language, under the above conditions for modified versions.
[all …]
|
| H A D | agentexpr.texi | 13 In some applications, it is not feasable for the debugger to interrupt
14 the program's execution long enough for the developer to learn anything
15 helpful about its behavior. If the program's correctness depends on its
16 real-time behavior, delays introduced by a debugger might cause the
17 program to fail, even when the code itself is correct. It is useful to
18 be able to observe the program's behavior without interrupting it.
20 Using GDB's @code{trace} and @code{collect} commands, the user can
21 specify locations in the program, and arbitrary expressions to evaluate
22 when those locations are reached. Later, using the @code{tfind}
23 command, she can examine the values those expressions had when the
[all …]
|
| /openbsd-src/share/snmp/ |
| H A D | SNMPv2-TC.txt | 37 Syntax ::= -- Must be one of the following:
54 "Represents textual information taken from the NVT ASCII
58 To summarize RFC 854, the NVT ASCII repertoire specifies:
60 - the use of character codes 0-127 (decimal)
62 - the graphics characters (32-126) are interpreted as
65 - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
68 - the other 25 codes have no standard interpretation
70 - the sequence 'CR LF' means newline
72 - the sequence 'CR NUL' means carriage-return
74 - an 'LF' not preceded by a 'CR' means moving to the
[all …]
|
| /openbsd-src/gnu/llvm/llvm/docs/TableGen/ |
| H A D | BackGuide.rst | 14 information from source files that are significantly easier to code than the
18 to various backends, which extract information from a subset of the records
20 for C++, but may be any type of file that the backend developer needs.
23 complete reference manual, but rather a guide to using the facilities
24 provided by TableGen for the backends. For a complete reference to the
25 various data structures and functions involved, see the primary TableGen
26 header file (``record.h``) and/or the Doxygen documentation.
28 This document assumes that you have read the :doc:`TableGen Programmer's
30 TableGen source files. For a description of the existing backends, see
36 The following sections describe the data structures that contain the classes
[all …]
|
| /openbsd-src/gnu/gcc/libmudflap/ |
| H A D | config.h.in | 3 /* Define to the name of the symbol used for the entry point. */
6 /* Define to 1 if you have the `addmntent' function. */
9 /* Define to 1 if you have the <arpa/inet.h> header file. */
12 /* Define to 1 if you have the `backtrace' function. */
15 /* Define to 1 if you have the `backtrace_symbols' function. */
18 /* Define to 1 if you have the <ctype.h> header file. */
21 /* Define to 1 if you have the `cuserid' function. */
24 /* Define to 1 if you have the <dirent.h> header file. */
27 /* Define to 1 if you have the <dlfcn.h> header file. */
30 /* Define to 1 if you have the `dlvsym' function. */
[all …]
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/ |
| H A D | gcc.hlp | 3 The GCC command invokes the GNU C compiler.
12 assumes .C as the default extension unless the /PLUS qualifier is
13 given, in which case .CC is assumed as the default extension.
15 If an extension of .CPP is given, then the source file is assumed to
16 be the output of the preprocessor, and thus the preprocessor is not
19 If an extension of .S is given, then the source file is assumed to be
20 the assembly code output of the compiler, and only the assembler is
25 GNU C command qualifiers modify the way the compiler handles the
28 The following is the list of available qualifiers for GNU C:
51 When linking programs compiled with GNU C, you should include the GNU
[all …]
|
| /openbsd-src/gnu/gcc/gcc/config/c4x/ |
| H A D | c4x-modes.def | 10 it under the terms of the GNU General Public License as published by
11 the Free Software Foundation; either version 2, or (at your option)
14 GCC is distributed in the hope that it will be useful,
15 but WITHOUT ANY WARRANTY; without even the implied warranty of
16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
19 You should have received a copy of the GNU General Public License
20 along with GCC; see the file COPYING. If not, write to
21 the Free Software Foundation, 51 Franklin Street, Fifth Floor,
26 the other modes it doesn't use. */
32 /* Add any extra modes needed to represent the condition code.
[all …]
|
| /openbsd-src/games/hunt/ |
| H A D | README.protocol | 5 These are some notes on the traditional INET protocol between hunt(6) and
6 huntd(6) as divined from the source code.
8 (In the original hunt, AF_UNIX sockets were used, but they are not
12 act as dumb 'graphics' clients in that they mostly only ever relay the
13 user's keystrokes to the server, and the server usually only ever sends
14 screen-drawing commands to the client. ie, the server does all the work.
24 the following sections.
26 Lines starting with "C:" and "S:" will indicate messages sent from the
31 This server port is used only to query simple information about the
32 game such as the port numbers of the other two ports (S and P),
[all …]
|