Home
last modified time | relevance | path

Searched full:useful (Results 1 – 25 of 3254) sorted by relevance

12345678910>>...131

/freebsd/lib/libpmc/pmu-events/arch/x86/amdzen3/
H A Dfloating-point.json46 …. See 2.1.17.3 [Large Increment per Cycle Events]. It does not provide a useful count without the …
52 …. See 2.1.17.3 [Large Increment per Cycle Events]. It does not provide a useful count without the …
58 …. See 2.1.17.3 [Large Increment per Cycle Events]. It does not provide a useful count without the …
64 …. See 2.1.17.3 [Large Increment per Cycle Events]. It does not provide a useful count without the …
70 …Scalar Ops optimized. This is a dispatch based speculative event, and is useful for measuring the …
76 … either set or pass). This is a dispatch based speculative event, and is useful for measuring the …
82 … Move Ops eliminated. This is a dispatch based speculative event, and is useful for measuring the …
88 …mber of SSE Move Ops. This is a dispatch based speculative event, and is useful for measuring the …
/freebsd/sbin/sysctl/
H A Dsysctl.885 This is mostly useful with a single variable.
91 This is useful for producing output which can be fed back to the
102 most useful with struct types such as clockinfo, timeval, and loadavg.
133 This is particularly useful with shells that offer programmable
150 This option is useful for setting shell variables.
172 Useful for determining the set of runtime tunable sysctls.
192 The opaque information is much more useful if retrieved by special
/freebsd/usr.bin/dtc/
H A Ddtc.179 This argument is only useful when the input is DTS, as only the source format
157 This is useful if you are generating a device tree blob for bootloader or
164 This is useful for environments where the device tree blob must be modified in
170 This is useful for environments where the device tree blob must be modified in
178 This is mainly useful when using tools like
339 This is useful when debugging device trees.
436 This is only useful in the assembly output, and only vaguely useful there, so
/freebsd/contrib/ntp/scripts/
H A DREADME9 monitoring directory containing perl scripts useful for monitoring
15 Useful at boot time, to delay the boot sequence
24 stats directory containing awk and shell scripts useful for
/freebsd/crypto/heimdal/doc/
H A Dwin2k.texi14 things to work rather than how they work, and not that useful in figuring
17 somewhat useful.
26 * Useful links when reading about the Windows::
230 @item The tool @kbd{lib/asn1/asn1_print} is somewhat useful for
234 @node Quirks of Windows 2000 KDC, Useful links when reading about the Windows, Authorisation data, …
266 @node Useful links when reading about the Windows, , Quirks of Windows 2000 KDC, Windows compatibi…
268 @section Useful links when reading about the Windows
292 Links to useful other links.
310 Other useful programs include these:
/freebsd/contrib/libxo/doc/
H A Dfaq.rst128 To make useful, consistent field names, follow these guidelines:
147 making consistent, useful names, avoiding the situation where one app
173 Have empathy for your users, choosing clear and useful fields that
174 contain clear and useful data. You may need to augment the display
176 fields (:ref:`encoding-modifier`) to make the data useful.
186 Think of your field vocabulary as an API. You want it useful,
/freebsd/share/doc/usd/07.mail/
H A Dmail5.nr31 This section describes some additional commands useful for
49 command is particularly useful in conjunction with some of the
181 command is especially useful for replying to messages that were sent
255 They are useful for quickly reading and disposing of mail.
463 .\"Define a list of local names for this host. This command is useful
604 It is often useful to be able to save messages on related topics
686 commands from a file. It is useful when you are trying to fix your
722 It is often useful to be able to invoke one of two editors,
766 command is useful for such tasks as sending and receiving
860 automatically. This is useful when quickly scanning and deleting
[all …]
/freebsd/contrib/llvm-project/llvm/include/llvm/DebugInfo/MSF/
H A DMSFBuilder.h35 /// at least `MinBlockCount` blocks. This is useful when using `MSFBuilder`
49 /// useful in testing scenarios when you know your test isn't going to do
62 /// Request the block map to be at a specific block address. This is useful
70 /// list of blocks. This is useful when reading a MSF file and you want a
77 /// blocks that the builder decides to use. This is useful when building a
/freebsd/contrib/llvm-project/llvm/utils/TableGen/Common/GlobalISel/
H A DCombinerUtils.h22 /// is primarily useful for testing for defs and similar in DagInit's since
33 /// primarily useful for testing for subclasses of GIDefKind and similar in
43 /// is a specific def and coerce it to a dag if it is. This is primarily useful
58 /// is. This is primarily useful for testing for subclasses of GIDefKind and
/freebsd/usr.bin/clang/bugpoint/
H A Dbugpoint.142 and JIT compilers). It aims to reduce large test cases to small, useful ones.
52 run. This is useful if you are debugging programs which depend on non\-LLVM
242 be useful for cross\-compilation.
255 This can be useful for
291 program to stderr. This is useful to make sure it is the same error being
/freebsd/share/doc/usd/12.vi/viapwh/
H A Dvi.apwh.ms334 useful for finding the beginnings of C functions.
341 or brace. This is very useful in C or lisp code. If the
411 search direction. This is useful if you overshoot.
536 some variations useful in getting and putting text into a file.
592 useful. They are:
599 Redraw the current screen. This is useful if someone "write"s you
610 "Dot" is a particularly useful command. It repeats the last
648 have the output of the command replace the original text. Useful
675 restored. This is useful for putting "labels" at the left margin.
716 to this file and start over from the beginning". It is useful if
[all …]
/freebsd/contrib/sendmail/libsm/
H A DREADME11 Libsm is a library of generally useful C abstractions.
117 Set this to a useful buffer size for regular files if stat(2)
122 Set this to a useful maximum buffer size for other than
127 Set this to a useful minimum buffer size for other than
/freebsd/sys/contrib/zstd/programs/
H A DREADME.md21 This is useful to ensure this feature is not silently disabled.
42 This is useful to prevent silent feature disabling.
52 This is useful to prevent silent feature disabling.
62 This is useful to prevent silent feature disabling.
65 This can be useful to produce smaller binaries.
69 This can be useful to produce smaller binaries.
74 This can be useful to produce smaller binaries.
79 This can be useful to produce smaller binaries.
231 This functionality can be useful when `zstd` CLI is invoked in a way that doesn't allow passing arg…
/freebsd/contrib/dma/
H A Ddma.888 Useful for debugging.
179 Only useful together with the
227 Only useful together with
238 Most useful when
244 Only useful together with
/freebsd/sbin/dumpfs/
H A Ddumpfs.854 command is useful mostly for finding out certain file system
65 fragment size, which may be useful when recovering deleted data.
88 is not useful in this case so is omitted.
/freebsd/usr.sbin/autofs/
H A Dautomount.858 It is only useful with
67 This is useful when debugging configuration problems.
76 It is only useful with
/freebsd/sbin/ipf/ipsend/
H A Dipresend.130 Set the interface name to be the name supplied. This is useful with the
77 most useful input type, currently.
102 wide enough variety of packets for them to be all useful in testing.
/freebsd/contrib/tcp_wrappers/
H A Dhosts_options.5110 keepalive option can be useful when users turn off their machine while
111 it is still connected to a server. The keepalive option is not useful
155 "kmem"). The first form is useful with inetd implementations that run
156 all services with root privilege. The second form is useful for
/freebsd/crypto/openssl/doc/man3/
H A DUI_STRING.pod67 This is only useful for B<UIT_PROMPT> and B<UIT_VERIFY> type strings.
73 This is only useful for B<UIT_VERIFY> type strings.
78 This is only useful for B<UIT_PROMPT> and B<UIT_VERIFY> type strings.
98 only useful with normal C strings.
/freebsd/tools/tools/
H A DREADME4 A tool is something which is sometimes useful, and doesn't fit any of
24 struct fpreg offsets. The tool is useful on selected
44 man Scripts useful for working on man pages.
/freebsd/usr.sbin/bsdconfig/include/
H A Dusage.hlp37 Most screens offer a Help button - USE IT! It generally offers useful
52 press the Scroll Lock key again. This feature is most useful for
54 it's also useful when dealing with sub-shells or other "expert modes"
/freebsd/contrib/googletest/
H A DREADME.md67 certain way, making it useful for testing error-handling code
74 different input values, making it useful for testing functions that take
78 data types, making it useful for testing functions that work with different
120 result output. If your test runner understands TAP, you may find it useful.
/freebsd/lib/libc/rpc/
H A Drpc_soc.31549 This routine is useful for users who
1564 This routine is useful for users
1580 This routine is useful for users who wish to generate
1594 This routine is useful for users who wish to generate
1608 This routine is useful for users who wish to generate
1625 This routine is useful for users who wish to generate
1636 This routine is useful for users who wish to generate
1649 This routine is useful for users who wish to generate
1663 This routine is useful for users who wish to generate
/freebsd/contrib/llvm-project/llvm/include/llvm/Analysis/
H A DRegionPrinter.h50 /// Useful to call in the debugger.
61 /// Useful to call in the debugger.
70 /// Useful to call in the debugger.
/freebsd/contrib/llvm-project/lldb/source/Plugins/TraceExporter/docs/
H A Dhtr.rst3 The humongous amount of data processor traces like the ones obtained with Intel PT contain is not digestible to humans in its raw form. Given this, it is useful to summarize these massive traces by extracting useful information. Hierarchical Trace Representation (HTR) is the way lldb represents a summarized trace internally. HTR efficiently stores trace data and allows the trace data to be transformed in a way akin to compiler passes.
31 A *pass* is applied to a *layer* to extract useful information (summarization) and compress the trace representation into a new *layer*. The idea is to have a series of passes where each pass specializes in extracting certain information about the trace. Some examples of potential passes include: identifying functions, identifying loops, or a more general purpose such as identifying long sequences of instructions that are repeated (i.e. Basic Super Block). Below you will find a description of each pass currently implemented in lldb.

12345678910>>...131