Home
last modified time | relevance | path

Searched +refs:is +refs:effective +refs:target (Results 1 – 25 of 110) sorted by relevance

12345

/external/libcap-ng/libcap-ng-0.7/
DChangeLog4 - Fix possible segfaults when CAP_LAST_CAP is larger than the lookup table
8 - In netcap, make sure readlink is handled properly
10 - In netcap and pscap, ensure euid is initialized
23 - Fix effective capabilities read from file descriptor
27 - In netcap and pscap use the effective uid
52 - Use bit mask on effective capabilities check in have_capabilities
58 - If attr/xattr.h is not available disable file system capabilities
63 - Added more tests to the make check target
/external/llvm-project/lldb/source/Plugins/Process/gdb-remote/
DProcessGDBRemoteProperties.td8 def TargetDefinitionFile: Property<"target-definition-file", "FileSpec">,
11 Desc<"The file that provides the description for remote target registers.">;
15 …be used to get a hold of the process's loaded modules. This setting is only effective if lldb was …
/external/llvm-project/polly/docs/
DArchitecture.rst5 Polly is a loop optimizer for LLVM. Starting from LLVM-IR it detects and
6 extracts interesting loop kernels. For each kernel a mathematical model is
10 optimizations have been derived and applied, optimized LLVM-IR is regenerated
19 The standard LLVM pass pipeline as it is used in -O1/-O2/-O3 mode of clang/opt
21 phases. The first phase, we call it here **Canonicalization**, is a scalar
26 executed in the so-called **Inliner cycle**, This is again a set of **Scalar
29 pass pipeline, the primary goal of these passes is still canonicalization
35 perform some optimizations, their primary goal is still the simplification of
36 the program code. Loop invariant code motion is one such optimization that
40 **Target Specialization** phase is run, where IR complexity is deliberately
[all …]
/external/llvm-project/llvm/test/Transforms/LoopVectorize/AArch64/
Dmax-vf-for-interleaved.ll3 target datalayout = "e-m:e-i64:64-i128:128-n32:64-S128"
4 target triple = "aarch64--linux-gnu"
10 ; vectorization is 16 bytes. Normally, this would lead to a maximum VF of 4.
11 ; However, for interleaved groups, the effective VF is VF * IF, where IF is the
12 ; interleave factor. Here, the maximum safe dependence distance is recomputed
/external/llvm/test/Transforms/LoopVectorize/AArch64/
Dmax-vf-for-interleaved.ll3 target datalayout = "e-m:e-i64:64-i128:128-n32:64-S128"
4 target triple = "aarch64--linux-gnu"
10 ; vectorization is 16 bytes. Normally, this would lead to a maximum VF of 4.
11 ; However, for interleaved groups, the effective VF is VF * IF, where IF is the
12 ; interleave factor. Here, the maximum safe dependence distance is recomputed
/external/boringssl/src/
DFUZZING.md3 Modern fuzz testers are very effective and we wish to use them to ensure that no silly bugs creep i…
5 …est of BoringSSL be built with some changes that make fuzzing much more effective, but are complet…
49 … for fuzzing and run `./fuzz/minimise_corpuses.sh`. Note that minimisation is, oddly, often not id…
53is passed into CMake, BoringSSL builds with `BORINGSSL_UNSAFE_FUZZER_MODE` and `BORINGSSL_UNSAFE_D…
59 Additionally, if `BORINGSSL_UNSAFE_FUZZER_MODE` is set, BoringSSL will:
65 * Tickets are unencrypted and the MAC check is performed but ignored.
69 This is to prevent the fuzzer from getting stuck at a cryptographic invariant in the protocol.
73 …r/fuzzer_mode.json` contains the necessary suppressions. The `run_tests` target will pass appropri…
75 …ild in this mode, pass `-DNO_FUZZER_MODE=1` into CMake. This configuration is run in the same way …
/external/llvm-project/lldb/test/Shell/Register/
Dx86-fp-write.test3 # it is covered by TestRegisters.py::fp_special_purpose_register_read.
5 # REQUIRES: native && (target-x86 || target-x86_64)
12 # note: this needs to enable all registers for writes to be effective
37 # This test is run both on 32-bit and 64-bit systems, in order to test
Dx86-64-fp-write.test3 # it is covered by TestRegisters.py::fp_special_purpose_register_read.
5 # REQUIRES: native && target-x86_64
12 # note: this needs to enable all registers for writes to be effective
/external/llvm-project/lldb/docs/
Dlldb-platform-packets.txt1 Here is a brief overview of the packets that an lldb platform server
3 target device/system.
28 // ACK mode is now disabled.
34 // Describe the hardware and OS of the target system
41 // All numbers are base 10, os_version is a string that will be parsed as major.minor.patch.
47 // Report information about a binary on the target system
85 // Create a directory on the target system.
96 // response is F followed by the return value of the mkdir() call,
103 // Run a shell command on the target system, return the output.
115 // Response is F followed by the return value of the command (base 16),
[all …]
Dlldb-gdb-remote.txt6 discover information about a remote target without having to know anything up
26 // connection is reliable. This improves packet throughput and increases
50 // Low. Only needed if the remote target wants to launch a target after
63 Where A is followed by the length in bytes of the hex encoded argument,
81 // NB: key/value pairs are sent as-is so gdb-remote protocol meta characters
84 // should be used instead if it is available. If you don't want to
86 // the QEnvironmentHexEncoded packet over QEnvironment, if it is
90 // Low. Only needed if the remote target wants to launch a target after
110 // The only difference between this packet and QEnvironment is that the
111 // environment key-value pair is ascii hex encoded for transmission.
[all …]
/external/tensorflow/tensorflow/lite/g3doc/models/segmentation/
Doverview.md3 Image segmentation is the process of partitioning a digital image into multiple
5 is to simplify and/or change the representation of an image into something that
6 is more meaningful and easier to analyze.
9 The model will create a mask over the target objects with high accuracy.
15 If you are new to TensorFlow Lite and are working with Android or iOS, it is
47 _DeepLab_ is a state-of-art deep learning model for semantic image segmentation,
48 where the goal is to assign semantic labels (e.g. person, dog, cat) to every
53 Semantic image segmentation predicts whether each pixel of an image is
54 associated with a certain class. This is in contrast to
63 … objects at multiple scales with filters at multiple sampling rates and effective fields-of-views.…
[all …]
/external/deqp/doc/testspecs/GLES31/
Dfunctional.texture.border_clamp.txt14 distributed under the License is distributed on an "AS IS" BASIS,
46 rendering result is then verified. Test cases also generate a reference image
49 In formats.* subgroup, all GLES31 texture formats are tested. Each format is
54 not in the representable range of the internal format. The effective value is
60 In per_axis_wrap_mode.*, texture wrap mode is not same in all S, T, and R
61 directions. Wrapping is tested for 2D and 3D textures with multiple formats
68 not representable in the target formats. These components are expected to have
/external/tensorflow/third_party/mkl/
Dbuild_defs.bzl3 if_mkl is a conditional to check if we are building with MKL.
4 if_mkl_ml is a conditional to check if we are building with MKL-ML.
5 if_mkl_ml_only is a conditional to check for MKL-ML-only (no MKL-DNN) mode.
6 if_mkl_lnx_x64 is a conditional to check for MKL
7 if_enable_mkl is a conditional to check if building with MKL and MKL is enabled.
9 mkl_repository is a repository rule for creating MKL repository rule that can
12 * `TF_MKL_ROOT`: The root folder where a copy of libmkl is located.
50 """Shorthand to select() if building with MKL and the target is Linux x86-64.
53 if_true: expression to evaluate if building with MKL is enabled and the
54 target platform is Linux x86-64.
[all …]
/external/angle/extensions/
DANGLE_get_image.txt49 void GetTexImageANGLE(GLenum target, GLint level, GLenum format, GLenum type,
52 void GetRenderbufferImageANGLE(GLenum target, GLint level, GLenum format,
76 Add a paragraph: "If <pname> is IMPLEMENTATION_COLOR_READ_TYPE or
86 void GetTexImageANGLE(GLenum target, GLint level, GLenum format, GLenum type,
89 void GetRenderbufferImageANGLE(GLenum target, GLenum format, GLenum type,
92 For GetTexImageANGLE, <target> specifies the target to which the texture
93 object is bound. target must be one of TEXTURE_2D, TEXTURE_3D,
95 dimensional, two-dimensional array, cube map array respectively. <target>
99 For GetRenderbufferImageANGLE, <target> must be RENDERBUFFER.
101 <level> is a level-of-detail number, <format> is a pixel format from table 8.5,
[all …]
DANGLE_depth_texture.txt39 OpenGL ES 2.0 is required.
40 This extension is written against the OpenGL ES 2.0.25 specification
89 "The stencil index texture internal component is ignored if the base
90 internal format is DEPTH_STENCIL_OES.
150 is clamped to [0, 1], while the stencil index values are masked by 2^n-1,
151 where n is the number of stencil bits in the internal format resolution
160 table 3.8. Specifying a value for <internalformat> that is not one of the
162 not match <format>, the error INVALID_OPERATION is generated.
166 only if <target> is TEXTURE_2D. Using these formats in conjunction with
167 any other <target> will result in an INVALID_OPERATION error.
[all …]
/external/perfetto/protos/perfetto/trace/
Dmemory_graph.proto11 * distributed under the License is distributed on an "AS IS" BASIS,
22 // is a Chrome-only tracing feature, historically known as 'memory-infra'. See
24 // This is unrelated to the native or java heap profilers (those protos live
28 // Memory snapshot of a process. The snapshot contains memory data that is
51 // memory dump. The ID is only unique within this particular global dump
55 // Absolute name is a unique name for the memory node within the process
65 // is unsure about the existence of the actual memory. Unless a "strong"
66 // (non-weak is default) node that has an edge to the current node exists
70 // Size of the node in bytes, used to compute the effective size of the
75 // debuggable information about the memory. The size of the node is
[all …]
/external/llvm-project/openmp/docs/
DSupportAndFAQ.rst38 The FAQ is a work in progress and most of the expected content is not
55 To build an *effective* OpenMP offload capable compiler we recommend a two
58 will be build with all backends enabled. This initial (stage 1) Clang is used
59 to create a second Clang compiler that is offload capable as well as the
63 Generic information about building LLVM is available `here
72 If your build machine is not the target machine or automatic detection of the
75 - `CLANG_OPENMP_NVPTX_DEFAULT_ARCH=sm_XX` where `XX` is the architecture of your GPU, e.g, 80.
76 - `LIBOMPTARGET_NVPTX_COMPUTE_CAPABILITIES=YY` where `YY` is the numeric compute capacity of your G…
89 For now, the answer is most likely *no*. Please see :ref:`build_offload_capable_compiler`.
93 For now, the answer is most likely *no*. Please see :ref:`build_offload_capable_compiler`.
/external/llvm-project/llvm/docs/Frontend/
DPerformanceTips.rst12 The intended audience of this document is developers of language frontends
13 targeting LLVM IR. This document is home to a collection of tips on how to
24 mature frontend for LLVM is Clang. As a result, the further your IR gets from
25 what Clang might emit, the less likely it is to be effectively optimized. It
38 target triple. Without these pieces, non of the target specific optimization
43 make LLVM's inter-procedural optimizations much more effective.
46 of predecessors). Among other issues, the register allocator is known to
48 this guidance is that a unified return block with high in-degree is fine.
58 multiple basic blocks. The end result is that a following alloca instruction
63 SSA is the canonical form expected by much of the optimizer; if allocas can
[all …]
/external/llvm/docs/Frontend/
DPerformanceTips.rst12 The intended audience of this document is developers of language frontends
13 targeting LLVM IR. This document is home to a collection of tips on how to
24 mature frontend for LLVM is Clang. As a result, the further your IR gets from what Clang might emi…
37 target triple. Without these pieces, non of the target specific optimization
42 make LLVM's inter-procedural optimizations much more effective.
45 of predecessors). Among other issues, the register allocator is known to
47 this guidance is that a unified return block with high in-degree is fine.
57 multiple basic blocks. The end result is that a following alloca instruction
62 SSA is the canonical form expected by much of the optimizer; if allocas can
63 not be eliminated by Mem2Reg or SROA, the optimizer is likely to be less
[all …]
/external/pigweed/docs/
Dpython_build.rst12 Pigweed's Python code is exclusively managed by GN, but the GN-based build may
26 Python is an interpreted language, but it shares most build automation concerns
50 Pigweed's use of Python is different from many other projects. Pigweed is a
59 Pigweed is organized into distinct modules. In Python, each module is a separate
65 its dependencies, but ``pip`` is not aware of local packages until they are
70 <https://pypi.org/project/pypiserver/>`_ instance, but this is too cumbersome
105 Another challenge is configuration. Mypy and Pylint support using configuration
125 Pigweed aims to provide high quality software components and a fast, effective,
145 Existing Python tools may be effective for Python codebases, but their utility
146 is more limited in a multi-language project like Pigweed. The cost of bringing
[all …]
/external/libpcap/msdos/
Dreadme.dos38 tcpdump) compiled with libpcap. Work is underway to implement protected-
39 mode drivers for 32-bit targets (djgpp only). The 3Com 3c509 driver is
50 1. Watt-32 tcp/ip library. This library is *not* used to send or
56 2. Exception handler and disassember library (libexc.a) is needed if
61 3. Flex & Bison is used to generate parser for the filter handler
66 4. NASM assembler v 0.98 or later is required when building djgpp and
70 5. sed (Stream Editor) is required for doing `make depend'.
79 time) for djgpp is DLX 2.91 or later. This tool is for the generation
89 During that installation a environment variable `WATT_ROOT' is set.
90 This variable is used for building libpcap also (`WATT_INC' is
[all …]
/external/llvm-project/openmp/tools/archer/
DREADME.md25 Archer is distributed under the terms of the Apache License.
35 **Archer** is an OMPT tool which annotates OpenMP synchronization semantics for data race
38 Archer is automatically loaded for OpenMP applications which are compiled
45 This distribution of Archer is automatically built with the OpenMP runtime
109 by ~30% and runtime overhead by ~10%. This flag is useful for large OpenMP
128 the sequential part of an OpenMP program. (Only effective when OpenMP
129 runtime is initialized. In doubt, insert omp_get_max_threads() as first
159 Suppose our program is called *myprogram.c*:
198 Location is stack of main thread.
217 …href="mailto:simone@cs.utah.edu?Subject=[archer-slack] Slack Invitation" target="_top">Simone Atze…
[all …]
/external/python/cpython2/Doc/library/
Dos.rst18 * The design of all built-in operating system dependent modules of Python is
19 such that as long as the same functionality is available, it uses the same
25 through the :mod:`os` module, but using them is of course a threat to
28 * An "Availability: Unix" note means that this function is commonly found on
76 ``environ['HOME']`` is the pathname of your home directory (on some platforms),
77 and is equivalent to ``getenv("HOME")`` in C.
79 This mapping is captured the first time the :mod:`os` module is imported,
86 be called automatically when the mapping is modified.
99 If :func:`putenv` is not provided, a modified copy of this mapping may be
105 automatically when an item is deleted from ``os.environ``, and when
[all …]
/external/llvm/docs/
DCompileCudaWithLLVM.rst12 C/C++ with LLVM. It is aimed at both users who want to compile CUDA with LLVM
21 CUDA support is still in development and works the best in the trunk version
22 of LLVM. Below is a quick summary of downloading and building the trunk
103 The command line for compilation is similar to what you would use for C++.
116 ``<CUDA install path>`` is the root directory where you installed CUDA SDK,
117 typically ``/usr/local/cuda``. ``<GPU arch>`` is `the compute capability of
125 Although clang's CUDA implementation is largely compatible with NVCC's, you may
128 This is tricky, because NVCC may invoke clang as part of its own compilation
132 When clang is actually compiling CUDA code -- rather than being used as a
133 subtool of NVCC's -- it defines the ``__CUDA__`` macro. ``__CUDA_ARCH__`` is
[all …]
/external/guice/lib/build/
Dfelix-2.0.5.jar ... framework.BundleException String location java.io.InputStream is org.osgi.framework.Bundle result Object sm ...

12345