Home
last modified time | relevance | path

Searched full:memory (Results 1 – 25 of 6407) sorted by relevance

12345678910>>...257

/llvm-project/llvm/unittests/Support/
H A DMemoryTest.cpp9 #include "llvm/Support/Memory.h"
58 // Adds RW flags to permit testing of the resulting memory
61 case Memory::MF_READ: in getTestableEquivalent()
62 case Memory::MF_WRITE: in getTestableEquivalent()
63 case Memory::MF_READ|Memory::MF_WRITE: in getTestableEquivalent()
64 return Memory::MF_READ|Memory::MF_WRITE; in getTestableEquivalent()
65 case Memory::MF_READ|Memory::MF_EXEC: in getTestableEquivalent()
66 case Memory::MF_READ|Memory::MF_WRITE|Memory::MF_EXEC: in getTestableEquivalent()
67 case Memory::MF_EXEC: in getTestableEquivalent()
68 return Memory::MF_READ|Memory::MF_WRITE|Memory::MF_EXEC; in getTestableEquivalent()
[all …]
/llvm-project/llvm/test/Assembler/
H A Dmemory-attribute.ll3 ; CHECK: Function Attrs: memory(none)
5 declare void @fn_readnone2() memory(none)
7 ; CHECK: Function Attrs: memory(read)
9 declare void @fn_readonly() memory(read)
11 ; CHECK: Function Attrs: memory(write)
13 declare void @fn_writeonly() memory(write)
15 ; CHECK: Function Attrs: memory(readwrite)
17 declare void @fn_readwrite() memory(readwrite)
19 ; CHECK: Function Attrs: memory(argmem: read)
21 declare void @fn_argmem_read() memory(argmem: read)
[all …]
/llvm-project/clang/test/Sema/
H A Datomic-implicit-seq_cst.c4 // want to force explicit usage of memory order instead.
10 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_pre_inc()
14 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_pre_dec()
18 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_post_inc()
22 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_post_dec()
26 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_call()
30 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_plus()
34 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_minus()
38 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_logical_not()
42 …ning {{implicit use of sequentially-consistent atomic may incur stronger memory barriers than nece… in bad_unary_bitwise_not()
[all …]
/llvm-project/llvm/test/tools/llvm-rc/
H A Dmemoryflags.test7 ; CHECK-NEXT: Memory flags: 0x1050
11 ; CHECK-NEXT: Memory flags: 0x1050
15 ; CHECK-NEXT: Memory flags: 0x1010
19 ; CHECK-NEXT: Memory flags: 0x1030
23 ; CHECK-NEXT: Memory flags: 0x0
27 ; CHECK-NEXT: Memory flags: 0x1030
31 ; CHECK-NEXT: Memory flags: 0x1010
35 ; CHECK-NEXT: Memory flags: 0x1030
39 ; CHECK-NEXT: Memory flags: 0x1030
43 ; CHECK-NEXT: Memory flags: 0x1030
[all …]
/llvm-project/libcxx/test/libcxx/atomics/
H A Ddiagnose_invalid_memory_order.verify.cpp13 // Test that invalid memory order arguments are diagnosed where possible.
24 x.load(std::memory_order_release); // expected-warning {{memory order argument to atomic operation is invalid}} in f()
25 x.load(std::memory_order_acq_rel); // expected-warning {{memory order argument to atomic operation is invalid}} in f()
26 vx.load(std::memory_order_release); // expected-warning {{memory order argument to atomic operation is invalid}} in f()
27 vx.load(std::memory_order_acq_rel); // expected-warning {{memory order argument to atomic operation is invalid}} in f()
28 // valid memory orders in f()
35 std::atomic_load_explicit(&x, std::memory_order_release); // expected-warning {{memory order argument to atomic operation is invalid}} in f()
36 std::atomic_load_explicit(&x, std::memory_order_acq_rel); // expected-warning {{memory order argument to atomic operation is invalid}} in f()
37 std::atomic_load_explicit(&vx, std::memory_order_release); // expected-warning {{memory order argument to atomic operation is invalid}} in f()
38 std::atomic_load_explicit(&vx, std::memory_order_acq_rel); // expected-warning {{memory orde in f()
[all...]
/llvm-project/llvm/test/Transforms/InstCombine/
H A Datomicrmw.ll403 …ra [[META0:![0-9]+]], !amdgpu.no.fine.grained.host.memory [[META1:![0-9]+]], !amdgpu.no.remote.mem…
406 …syncscope("agent") monotonic, !amdgpu.no.fine.grained.host.memory !0, !amdgpu.no.remote.memory.acc…
412 …align 4, !mmra [[META0]], !amdgpu.no.fine.grained.host.memory [[META1]], !amdgpu.no.remote.memory.…
415 …syncscope("agent") monotonic, !amdgpu.no.fine.grained.host.memory !0, !amdgpu.no.remote.memory.acc…
422 …align 4, !mmra [[META0]], !amdgpu.no.fine.grained.host.memory [[META1]], !amdgpu.no.remote.memory.…
425 …syncscope("agent") monotonic, !amdgpu.no.fine.grained.host.memory !0, !amdgpu.no.remote.memory.acc…
432 …align 4, !mmra [[META0]], !amdgpu.no.fine.grained.host.memory [[META1]], !amdgpu.no.remote.memory.…
435 …syncscope("agent") monotonic, !amdgpu.no.fine.grained.host.memory !0, !amdgpu.no.remote.memory.acc…
442 …align 4, !mmra [[META0]], !amdgpu.no.fine.grained.host.memory [[META1]], !amdgpu.no.remote.memory.…
445 …syncscope("agent") monotonic, !amdgpu.no.fine.grained.host.memory !0, !amdgpu.no.remote.memory.acc…
[all …]
/llvm-project/compiler-rt/test/msan/
H A Dchained_origin_limits.cpp4 // RUN: %clangxx_msan -fsanitize-memory-track-origins=2 -O3 %s -o %t
19 // RUN: %clangxx_msan -DSTACK -fsanitize-memory-track-origins=2 -O3 %s -o %t
34 // RUN: %clangxx_msan -mllvm -msan-instrumentation-with-call-threshold=0 -fsanitize-memory-track-origins=2 -O3 %s -o %t
49 // RUN: %clangxx_msan -DSTACK -mllvm -msan-instrumentation-with-call-threshold=0 -fsanitize-memory-track-origins=2 -O3 %s -o %t
127 // CHECK7-NOT: Uninitialized value was stored to memory at
128 // CHECK7: Uninitialized value was stored to memory at
129 // CHECK7-NOT: Uninitialized value was stored to memory at
130 // CHECK7: Uninitialized value was stored to memory at
131 // CHECK7-NOT: Uninitialized value was stored to memory at
132 // CHECK7: Uninitialized value was stored to memory a
[all...]
/llvm-project/llvm/lib/Support/rpmalloc/
H A DREADME.md1 # rpmalloc - General Purpose Memory Allocator
2 This library provides a cross platform lock free thread caching 16-byte aligned memory allocator im…
14 …with atomic operations and an mmap-style virtual memory management API. The API used to map/unmap …
19 …s faster than most popular memory allocators like tcmalloc, hoard, ptmalloc3 and others without ca…
21 …s. It measures number of memory operations performed per CPU second, as well as memory overhead by…
37 … call __rpmalloc_finalize__ in order to release caches and unmap virtual memory, as well as prepar…
44 …l at process start to initialize the allocator with a custom memory mapping backend, memory page s…
68 Free memory pages are cached both per thread and in a global cache for all threads. The size of the…
70 …che unless thread finishes and never unmap memory pages back to the OS. Highest performance but la…
72 …t defined to 0, set to 1 to make global caches infinite, i.e never unmap memory pages back to the …
[all …]
H A Drpmalloc.h76 //! Current amount of virtual memory mapped, all of which might not have been
79 //! Peak amount of virtual memory mapped, all of which might not have been
82 //! Current amount of memory in global caches for small and medium sizes
85 //! Current amount of memory allocated in huge allocations, i.e larger than
88 //! Peak amount of memory allocated in huge allocations, i.e larger than
91 //! Total amount of memory mapped since initialization (only if
94 //! Total amount of memory unmapped since initialization (only if
130 //! Number of raw memory map calls (not hitting the reserve spans but
150 //! Number of raw memory map calls (not hitting the reserve spans but
157 //! Map memory pages for the given number of bytes. The returned address MUST
[all …]
/llvm-project/lld/test/wasm/
H A Dimport-memory.test2 # RUN: wasm-ld --import-memory -o %t.wasm %t.start.o
5 # Verify the --import-memory flag creates a memory import
10 # CHECK-NEXT: Field: memory
11 # CHECK-NEXT: Kind: MEMORY
12 # CHECK-NEXT: Memory:
18 # RUN: wasm-ld --import-memory --initial-memory=262144 \
19 # RUN: --max-memory=327680 -o %t.max.wasm %t.start.o
22 # Verify the --initial-memory and --max-memory arguments work with imports
27 # CHECK-MAX-NEXT: Field: memory
28 # CHECK-MAX-NEXT: Kind: MEMORY
[all …]
H A Dmemory-naming.test2 # RUN: wasm-ld --export-memory=foo -o %t.wasm %t.start.o
5 # Verify that the --export-memory=<name> option changes the exported name of the module's memory
10 # CHECK-NEXT: Kind: MEMORY
17 # RUN:wasm-ld --export-memory --export-memory -o %t.unnamed.wasm %t.start.o
20 # Verify that the --export-memory option without a parameter exports the memory
21 # as "memory"
25 # CHECK-UNNAMED-NEXT: - Name: memory
26 # CHECK-UNNAMED-NEXT: Kind: MEMORY
33 # RUN:wasm-ld --export-memory=foo --export-memory=foo -o %t.duplicate.wasm %t.start.o
36 # Verify that passing --export-memory with the same name twice works
[all …]
H A Dshared-memory.yaml3 # RUN: wasm-ld --no-entry --shared-memory --features=atomics,bulk-memory %t1.o -o - | obj2yaml | Fi…
5 # RUN: not wasm-ld --no-entry --shared-memory --max-memory=100000 %t1.o -o - 2>&1 | FileCheck %s --…
7 # RUN: not wasm-ld --no-entry --shared-memory --max-memory=131072 --features=bulk-memory %t1.o -o -…
9 # RUN: not wasm-ld --no-entry --shared-memory --max-memory=131072 --features=atomics %t1.o -o - 2>&…
13 # RUN: wasm-ld --no-entry --shared-memory --max-memory=131072 --features=atomics,bulk-memory %t1.o …
23 Kind: MEMORY
24 Memory:
59 # SHARED-UNALIGNED: maximum memory must be 65536-byte aligned{{$}}
61 # SHARED-NO-ATOMICS: 'atomics' feature must be used in order to use shared memory
63 # SHARED-NO-BULK-MEM: 'bulk-memory' feature must be used in order to use shared memory
[all …]
/llvm-project/lldb/test/Shell/Minidump/
H A Dmemory-region-from-module.yaml1 # Check that memory region parsing works correctly, with a particular emphasis
6 # RUN: yaml2obj %S/Inputs/basic-elf.yaml -o %T/memory-region-from-module.exe
8 # RUN: %lldb -b -c %t1.dmp %T/memory-region-from-module.exe \
9 # RUN: -o "memory region 0" -o "memory region 0x4000" \
10 # RUN: -o "memory region 0x5000" -o "memory region 0x6000" \
13 # RUN: %lldb -b -c %t2.dmp %T/memory-region-from-module.exe \
14 # RUN: -o "memory region 0" -o "memory region 0x4000" \
15 # RUN: -o "memory region 0x5000" -o "memory region 0x6000" \
18 # ALL-LABEL: (lldb) memory region 0
20 # ALL-LABEL: (lldb) memory region 0x4000
[all …]
/llvm-project/llvm/include/llvm/Support/
H A DMemory.h1 //===- llvm/Support/Memory.h - Memory Support -------------------*- C++ -*-===//
9 // This file declares the llvm::sys::Memory class.
27 /// This class encapsulates the notion of a memory block which has an address
28 /// and a size. It is used by the Memory class (a friend) as the result of
29 /// various memory allocation operations.
30 /// @see Memory
31 /// Memory block abstraction.
43 void *Address; ///< Address of first byte of memory area
44 size_t AllocatedSize; ///< Size, in bytes of the memory are
45 friend class Memory; global() variable
[all...]
H A DModRef.h1 //===--- ModRef.h - Memory effect modeling ----------------------*- C++ -*-===//
10 // describe the memory effects of instructions.
23 /// Flags indicating whether a memory access modifies or references memory.
28 /// The access neither references nor modifies the value stored in memory.
30 /// The access may reference the value stored in memory.
32 /// The access may modify the value stored in memory.
34 /// The access may reference and may modify the value stored in memory.
58 /// The locations at which a function might access memory.
60 /// Access to memory vi
[all...]
/llvm-project/clang/test/Driver/
H A Dfsanitize-memory-param-retval.c1 // RUN: %clang --target=i386-gnu-linux %s -fsanitize=memory -fno-sanitize-memory-param-retval -c -#…
2 // RUN: %clang --target=x86_64-linux-gnu %s -fsanitize=memory -fno-sanitize-memory-param-retval -c …
3 // RUN: %clang --target=aarch64-linux-gnu %s -fsanitize=memory -fno-sanitize-memory-param-retval -c…
4 // RUN: %clang --target=riscv32-linux-gnu %s -fsanitize=memory -fno-sanitize-memory-param-retval -c…
5 // RUN: %clang --target=riscv64-linux-gnu %s -fsanitize=memory -fno-sanitize-memory-param-retval -c…
6 // RUN: %clang --target=x86_64-linux-gnu %s -fsanitize=kernel-memory -fno-sanitize-memory-param-ret…
8 // CHECK: "-fno-sanitize-memory-param-retval"
10 // RUN: %clang --target=aarch64-linux-gnu -fsyntax-only %s -fsanitize=memory -fno-sanitize-memory-p…
11 // 11: "-fno-sanitize-memory-param-retval"
13 …t %clang --target=x86_64-linux-gnu -fsyntax-only %s -fsanitize=memory -fno-sanitize-memory-param-r…
[all …]
H A Dmsan.c1 // RUN: %clang --target=mips64-linux-gnu -fsanitize=memory %s -S -emit-llvm -o - | FileCheck %s --c…
2 // RUN: %clang --target=mips64el-unknown-linux-gnu -fsanitize=memory %s -S -emit-llvm -o - | FileCh…
3 // RUN: %clang --target=powerpc64-unknown-linux-gnu -fsanitize=memory %s -S -emit-llvm -o - | FileC…
4 // RUN: %clang --target=powerpc64le-unknown-linux-gnu -fsanitize=memory %s -S -emit-llvm -o - | Fil…
6 // Verify that -fsanitize=memory and -fsanitize=kernel-memory invoke MSan/KMSAN instrumentation.
8 // RUN: %clang --target=x86_64-unknown-linux -fsanitize=memory %s -S -emit-llvm -o - | FileChec…
9 // RUN: %clang -O1 --target=x86_64-unknown-linux -fsanitize=memory %s -S -emit-llvm -o - | FileChec…
10 // RUN: %clang -O2 --target=x86_64-unknown-linux -fsanitize=memory %s -S -emit-llvm -o - | FileChec…
11 // RUN: %clang -O3 --target=x86_64-unknown-linux -fsanitize=memory %s -S -emit-llvm -o - | FileChec…
12 // RUN: %clang --target=x86_64-unknown-linux -fsanitize=memory %s -S -emit-llvm -flto=thin -o -…
[all …]
/llvm-project/lldb/test/API/linux/aarch64/mte_tag_access/
H A DTestAArch64LinuxMTEMemoryTagAccess.py2 Test "memory tag read" and "memory tag write" commands
21 # other than the memory tags.
54 "memory tag read",
62 "memory tag read mte_buf buf+16 32",
70 "memory tag read not_a_symbol",
78 "memory tag read mte_buf not_a_symbol",
87 "memory tag read mte_buf mte_buf-16",
96 "memory tag read mte_buf mte_buf",
106 "memory tag read non_mte_buf",
109 "in a memory tagged region"
[all …]
/llvm-project/flang/test/Semantics/OpenMP/
H A Datomic01.f9014 ! At most one memory-order-clause may appear on the construct.
17 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
21 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
25 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
30 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
34 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
38 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
43 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
47 !ERROR: More than one memory order clause not allowed on OpenMP ATOMIC construct
51 !ERROR: More than one memory orde
[all...]
/llvm-project/lldb/include/lldb/API/
H A DSBMemoryRegionInfo.h34 /// Get the base address of this memory range.
37 /// The base address of this memory range.
40 /// Get the end address of this memory range.
43 /// The base address of this memory range.
46 /// Check if this memory address is marked readable to the process.
49 /// true if this memory address is marked readable
52 /// Check if this memory address is marked writable to the process.
55 /// true if this memory address is marked writable
58 /// Check if this memory address is marked executable to the process.
61 /// true if this memory addres
[all...]
/llvm-project/clang/test/Analysis/
H A DNewDeleteLeaks.cpp24 // allocated memory, but in this instance, its also the only function with
32 sink(new int(5)); // expected-note {{Memory is allocated}} in foo()
33 } // expected-warning {{Potential memory leak [cplusplus.NewDeleteLeaks]}} in foo()
34 // expected-note@-1 {{Potential memory leak}}
38 // Realize that sink() intends to deallocate memory, assume that it should've
46 } // ownership-note {{Returning without deallocating memory or storing the pointer for later deallo… in sink()
49 int *ptr = new int(5); // expected-note {{Memory is allocated}} in foo()
52 } // expected-warning {{Potential leak of memory pointed to by 'ptr' [cplusplus.NewDeleteLeaks]}} in foo()
63 } // ownership-note {{Returning without deallocating memory or storing the pointer for later deallo… in sink()
66 int *ptr = (int *)malloc(sizeof(int)); // expected-note {{Memory is allocated}} in foo()
[all …]
/llvm-project/llvm/include/llvm/ExecutionEngine/
H A DSectionMemoryManager.h1 //===- SectionMemoryManager.h - Memory manager for MCJIT/RtDyld -*- C++ -*-===//
9 // This file contains the declaration of a section-based memory manager used by
19 #include "llvm/Support/Memory.h"
26 /// This is a simple memory manager which implements the methods called by
27 /// the RuntimeDyld class to allocate memory for section-based loading of
30 /// This memory manager allocates all section memory as read-write. The
31 /// RuntimeDyld will copy JITed section memory into these allocated blocks
34 /// Any client using this memory manager MUST ensure that section-specific
53 /// This method attempts to allocate \p NumBytes bytes of virtual memory for
55 /// case an attempt is made to allocate more memory near the existing block.
[all …]
/llvm-project/lldb/test/API/commands/memory/read/
H A DTestMemoryRead.py2 Test the 'memory read' command.
22 """Test that reading memory as a c string respects the size limit given
26 # The size here is the size in memory so it includes the null terminator.
27 cmd = 'memory read --format "c-string" --size {} &my_string'
45 """Test the 'memory read' command with plain and vector formats."""
48 # (lldb) memory read -f d -c 1 `&argc`
50 self.runCmd("memory read -f d -c 1 `&argc`")
62 # (lldb) memory read --format uint32_t[] --size 4 --count 4 `&argc`
67 self.runCmd("memory read --format uint32_t[] --size 4 --count 4 `&argc`")
77 # (lldb) memory read --format char[] --size 7 --count 1 `&my_string`
[all …]
/llvm-project/lldb/test/API/linux/aarch64/mte_core_file/
H A DTestAArch64LinuxMTEMemoryTagCoreFile.py2 Test that memory tagging features work with Linux core files.
18 """Test that memory regions are marked as tagged when there is a tag
23 self.runCmd("memory region --all")
28 if "memory tagging: enabled" in line:
33 self.assertTrue(found_tagged_region, "Did not find a tagged memory region.")
36 tagged = "memory tagging: enabled"
37 self.expect("memory region {}".format(self.MTE_BUF_ADDR), patterns=[tagged])
39 "memory region {}".format(self.BUF_ADDR), patterns=[tagged], matching=False
44 """Test that "memory tag write" does not work with core files
49 "memory ta
[all...]
/llvm-project/llvm/test/Transforms/FunctionAttrs/
H A Dnorecurse.ll7 ; FNATTRS: Function Attrs: mustprogress nofree norecurse nosync nounwind willreturn memory(none)
12 ; ATTRIBUTOR: Function Attrs: mustprogress nofree norecurse nosync nounwind willreturn memory(none)
21 ; FNATTRS: Function Attrs: nofree nosync nounwind memory(none)
27 ; ATTRIBUTOR: Function Attrs: nofree nosync nounwind memory(none)
38 ; FNATTRS: Function Attrs: nofree nosync nounwind memory(none)
44 ; ATTRIBUTOR: Function Attrs: nofree nosync nounwind memory(none)
55 ; FNATTRS: Function Attrs: nofree nosync nounwind memory(none)
61 ; ATTRIBUTOR: Function Attrs: nofree nosync nounwind memory(none)
72 ; FNATTRS: Function Attrs: nofree nosync memory(none)
78 ; ATTRIBUTOR: Function Attrs: nosync memory(non
[all...]

12345678910>>...257