Home
last modified time | relevance | path

Searched refs:regions (Results 1 – 25 of 186) sorted by relevance

12345678

/openbsd/src/gnu/llvm/lldb/source/Plugins/Process/minidump/
DMinidumpParser.cpp259 std::vector<MemoryRegionInfo> &regions) { in CreateRegionsCacheFromLinuxMaps() argument
267 [&regions, &log](llvm::Expected<MemoryRegionInfo> region) -> bool { in CreateRegionsCacheFromLinuxMaps()
269 regions.push_back(*region); in CreateRegionsCacheFromLinuxMaps()
275 return !regions.empty(); in CreateRegionsCacheFromLinuxMaps()
329 const MemoryRegionInfos &regions, in CheckForLinuxExecutable() argument
331 if (regions.empty()) in CheckForLinuxExecutable()
334 MemoryRegionInfo region = MinidumpParser::GetMemoryRegionInfo(regions, addr); in CheckForLinuxExecutable()
339 region = MinidumpParser::GetMemoryRegionInfo(regions, addr); in CheckForLinuxExecutable()
517 std::vector<MemoryRegionInfo> &regions) { in CreateRegionsCacheFromMemoryInfoList() argument
547 regions.push_back(region); in CreateRegionsCacheFromMemoryInfoList()
[all …]
DMinidumpParser.h99 static MemoryRegionInfo GetMemoryRegionInfo(const MemoryRegionInfos &regions,
/openbsd/src/sys/dev/pci/drm/i915/gem/selftests/
Di915_gem_dmabuf.c96 struct intel_memory_region *lmem = i915->mm.regions[INTEL_REGION_LMEM_0]; in igt_dmabuf_import_same_driver_lmem()
220 struct intel_memory_region **regions, in igt_dmabuf_import_same_driver() argument
234 regions, num_regions); in igt_dmabuf_import_same_driver()
278 if (obj->mm.region != i915->mm.regions[INTEL_REGION_SMEM]) { in igt_dmabuf_import_same_driver()
326 struct intel_memory_region *smem = i915->mm.regions[INTEL_REGION_SMEM]; in igt_dmabuf_import_same_driver_smem()
334 struct intel_memory_region *regions[2]; in igt_dmabuf_import_same_driver_lmem_smem() local
336 if (!i915->mm.regions[INTEL_REGION_LMEM_0]) in igt_dmabuf_import_same_driver_lmem_smem()
339 regions[0] = i915->mm.regions[INTEL_REGION_LMEM_0]; in igt_dmabuf_import_same_driver_lmem_smem()
340 regions[1] = i915->mm.regions[INTEL_REGION_SMEM]; in igt_dmabuf_import_same_driver_lmem_smem()
341 return igt_dmabuf_import_same_driver(i915, regions, 2); in igt_dmabuf_import_same_driver_lmem_smem()
Di915_gem_migrate.c50 struct intel_memory_region *src_mr = i915->mm.regions[src]; in igt_create_migrate()
51 struct intel_memory_region *dst_mr = i915->mm.regions[dst]; in igt_create_migrate()
/openbsd/src/gnu/llvm/clang/tools/clang-format/
Dclang-format-sublime.py34 regions = []
39 regions.append(region)
56 for region in regions:
/openbsd/src/sys/dev/pci/drm/i915/
Dintel_memory_region.c337 for (i = 0; i < ARRAY_SIZE(i915->mm.regions); i++) { in intel_memory_regions_hw_probe()
379 i915->mm.regions[i] = mem; in intel_memory_regions_hw_probe()
383 for (i = 0; i < ARRAY_SIZE(i915->mm.regions); i++) { in intel_memory_regions_hw_probe()
384 struct intel_memory_region *mem = i915->mm.regions[i]; in intel_memory_regions_hw_probe()
412 for (i = 0; i < ARRAY_SIZE(i915->mm.regions); i++) { in intel_memory_regions_driver_release()
414 fetch_and_zero(&i915->mm.regions[i]); in intel_memory_regions_driver_release()
Dintel_memory_region.h46 for (id = 0; id < ARRAY_SIZE((i915)->mm.regions); id++) \
47 for_each_if((mr) = (i915)->mm.regions[id])
/openbsd/src/gnu/llvm/llvm/docs/
DCoverageMappingFormat.rst60 regions of code, and emit the mapping information only for those regions.
77 The function's coverage mapping data contains an array of mapping regions.
81 There are several kinds of mapping regions:
83 * Code regions associate portions of source code and `coverage mapping
84 counters`_. They make up the majority of the mapping regions. They are used
86 highlight the regions of code that were never executed, and to obtain
100 * Skipped regions are used to represent source ranges that were skipped
114 * Expansion regions are used to represent Clang's macro expansions. They
116 used by the code coverage tool to find the mapping regions that are created
129 * Branch regions associate instrumentable branch conditions in the source code
[all …]
/openbsd/src/sys/dev/pci/drm/i915/gem/
Di915_gem_lmem.c105 return i915_gem_object_create_region(i915->mm.regions[INTEL_REGION_LMEM_0], in __i915_gem_object_create_lmem_with_ps()
141 return i915_gem_object_create_region(i915->mm.regions[INTEL_REGION_LMEM_0], in i915_gem_object_create_lmem()
Di915_gem_create.c53 obj->mm.placements = &i915->mm.regions[mr->id]; in object_set_placements()
278 u64_to_user_ptr(args->regions); in set_placements()
293 BUILD_BUG_ON(ARRAY_SIZE(i915->mm.regions) != ARRAY_SIZE(placements)); in set_placements()
295 if (args->num_regions > ARRAY_SIZE(i915->mm.regions)) { in set_placements()
Di915_gem_ttm_pm.c83 backup = i915_gem_object_create_region(i915->mm.regions[INTEL_REGION_SMEM], in i915_ttm_backup()
/openbsd/src/gnu/llvm/clang/docs/analyzer/developer-docs/
DRegionStore.rst4 The analyzer "Store" represents the contents of memory regions. It is an opaque
9 ``RegionStoreManager``. This store records bindings to memory regions using a
13 Regions are grouped into "clusters", which roughly correspond to "regions with
71 fields, they are not base regions, and when their parent object region is
94 its entire cluster, since neighboring regions may be accessed via pointer
102 accessible regions is known as ClusterAnalysis, and is also used for finding
163 to super-regions to look for an appropriate default binding. LazyCompoundVal
DInitializerLists.rst61 So i believe that escaping metadata symbols whenever their base regions escape
66 metadata-symbolic-based regions during scanReachableSymbols() whenever a region
140 > metadata-symbolic-based regions during scanReachableSymbols() whenever
160 reachable from here exists another region of type T". Or even multiple regions
162 but it would allow for transfer functions to get at those regions and it would
167 end element regions for it.
193 > another region of type T". Or even multiple regions with different
195 > allow for transfer functions to get at those regions and it would allow for
212 > beginning and end element regions for it.
248 reachable symbols and regions) that cannot work without checker support.
[all …]
/openbsd/src/gnu/llvm/clang/docs/
DOpenMPSupport.rst64 Clang code generation for target regions supports two modes: the SPMD and
81 `Generic` mode all local variables that can be shared in the parallel regions
84 between the threads in the parallel regions.
96 - Nested parallelism: inner parallel regions are executed sequentially.
98 - Automatic translation of math functions in target regions to device-specific
101 - Debug information for OpenMP target regions is supported, but sometimes it may
324 | misc | routines for controlling and querying team regions | :no…
DSourceBasedCodeCoverage.rst157 ``-show-line-counts-or-regions`` is enabled, ``llvm-cov`` displays sub-line
270 * Region coverage is the percentage of code regions which have been executed at
273 contain multiple code regions (e.g in "return x || y && z").
314 from source regions to profile counters is immutable, and is generated before
418 Gap regions
421 Gap regions are source regions with counts. A reporting tool cannot set a line
425 Gap regions are used to eliminate unnatural artifacts in coverage reports, such
430 Branch regions
465 Branch regions are also generated for each switch case, including the default
/openbsd/src/gnu/gcc/libgomp/
Dlibgomp.texi138 * omp_get_nested:: Nested parallel regions
144 * omp_set_nested:: Enable/disable nested parallel regions
206 Return the maximum number of threads used for parallel regions that do
229 @section @code{omp_get_nested} -- Nested parallel regions
232 This function returns @code{true} if nested parallel regions are
236 Nested parallel regions may be initialized at startup by the
238 @code{omp_set_nested}. If undefined, nested parallel regions are
320 @code{omp_get_thread_num} always returns 0. In parallel regions the return
396 @section @code{omp_set_nested} -- Enable/disable nested parallel regions
399 Enable or disable nested parallel regions, i.e., whether team members
[all …]
/openbsd/src/sys/dev/ic/
Dsti.c417 struct sti_region regions[STI_REGION_MAX], *r; in sti_region_setup() local
433 *(u_int *)(regions + regno) = in sti_region_setup()
437 (u_int8_t *)regions, sizeof regions); in sti_region_setup()
446 for (regcnt = 0, r = regions; regcnt < STI_REGION_MAX; regcnt++, r++) in sti_region_setup()
455 for (regno = 0, r = regions; regno < regcnt; regno++, r++) { in sti_region_setup()
477 cc->regions[0] = addr; in sti_region_setup()
497 cc->regions[regno] = addr; in sti_region_setup()
505 if (cc->regions[regno] == 0) in sti_region_setup()
506 cc->regions[regno] = 0x81234567; in sti_region_setup()
/openbsd/src/regress/sys/kern/extent/
Dtests103 # Overlapping regions should result in a failure
140 # Check freeing overkapping regions from a filled extent
/openbsd/src/gnu/llvm/llvm/docs/CommandGuide/
Dllvm-cov.rst237 For source regions that are instantiated multiple times, such as templates in
241 .. option:: -show-regions
246 .. option:: -show-line-counts-or-regions
249 line, but show the individual regions if there are multiple on the line.
408 Show statistics for all regions. Defaults to true.
463 When exporting JSON, the regions, functions, branches, expansions, and
492 functions or regions. The result will contain the same information as produced
/openbsd/src/gnu/llvm/clang/lib/Headers/openmp_wrappers/
Dcomplex1 /*===-- complex --- OpenMP complex wrapper for target regions --------- c++ -===
/openbsd/src/gnu/llvm/compiler-rt/lib/lsan/
Dlsan_flags.inc35 "Root set: include regions added via __lsan_register_root_region().")
/openbsd/src/sys/arch/alpha/dev/
Dsgmap_typedep.c63 struct extent_region *regions = map->_dm_cookie; in __C() local
136 0, boundary, EX_NOWAIT, &regions[seg], &sgva); in __C()
/openbsd/src/gnu/llvm/clang/include/clang/StaticAnalyzer/Core/PathSensitive/
DRegions.def9 // The list of regions (MemRegion sub-classes) used in the Static Analyzer.
/openbsd/src/gnu/llvm/compiler-rt/lib/scudo/standalone/
Dwrappers_c.inc43 // Space allocated in mmapped regions (bytes)
61 // Space allocated in mmapped regions (bytes)
/openbsd/src/gnu/llvm/llvm/docs/Proposals/
DVectorizationPlan.rst80 6. Encapsulate Single-Entry Single-Exit regions (SESE). During vectorization
81 such regions may need to be, for example, predicated and linearized, or
83 Innerloops are also modelled as SESE regions.

12345678