From 972317651105e477e77a617ddedfaa5dc87d6437 Mon Sep 17 00:00:00 2001 From: Andrew Kaylor Date: Fri, 4 Oct 2013 20:09:36 +0000 Subject: Fixing container/pointer bug in remote-lli found by ASan llvm-svn: 191976 --- llvm/tools/lli/RemoteMemoryManager.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'llvm/tools/lli/RemoteMemoryManager.h') diff --git a/llvm/tools/lli/RemoteMemoryManager.h b/llvm/tools/lli/RemoteMemoryManager.h index dc746666726..ca157a79298 100644 --- a/llvm/tools/lli/RemoteMemoryManager.h +++ b/llvm/tools/lli/RemoteMemoryManager.h @@ -30,6 +30,7 @@ class RemoteMemoryManager : public JITMemoryManager { public: // Notice that this structure takes ownership of the memory allocated. struct Allocation { + Allocation() {} Allocation(sys::MemoryBlock mb, unsigned a, bool code) : MB(mb), Alignment(a), IsCode(code) {} @@ -48,11 +49,11 @@ private: // have allocated locally but have not yet remapped for the remote target. // When we receive notification of a completed module load, we will map // these sections into the remote target. - SmallVector UnmappedSections; + SmallVector UnmappedSections; // This map tracks the sections we have remapped for the remote target // but have not yet copied to the target. - DenseMap MappedSections; + DenseMap MappedSections; // FIXME: This is part of a work around to keep sections near one another // when MCJIT performs relocations after code emission but before -- cgit v1.2.3