mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2025-06-18 11:24:01 +00:00
Don't own the buffer in object::Binary.
Owning the buffer is somewhat inflexible. Some Binaries have sub Binaries (like Archive) and we had to create dummy buffers just to handle that. It is also a bad fit for IRObjectFile where the Module wants to own the buffer too. Keeping this ownership would make supporting IR inside native objects particularly painful. This patch focuses in lib/Object. If something elsewhere used to own an Binary, now it also owns a MemoryBuffer. This patch introduces a few new types. * MemoryBufferRef. This is just a pair of StringRefs for the data and name. This is to MemoryBuffer as StringRef is to std::string. * OwningBinary. A combination of Binary and a MemoryBuffer. This is needed for convenience functions that take a filename and return both the buffer and the Binary using that buffer. The C api now uses OwningBinary to avoid any change in semantics. I will start a new thread to see if we want to change it and how. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@216002 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
@ -28,7 +28,7 @@ class IRObjectFile : public SymbolicFile {
|
||||
std::vector<std::pair<std::string, uint32_t>> AsmSymbols;
|
||||
|
||||
public:
|
||||
IRObjectFile(std::unique_ptr<MemoryBuffer> Object, std::unique_ptr<Module> M);
|
||||
IRObjectFile(MemoryBufferRef Object, std::unique_ptr<Module> M);
|
||||
~IRObjectFile();
|
||||
void moveSymbolNext(DataRefImpl &Symb) const override;
|
||||
std::error_code printSymbolName(raw_ostream &OS,
|
||||
@ -49,9 +49,8 @@ public:
|
||||
return v->isIR();
|
||||
}
|
||||
|
||||
static ErrorOr<IRObjectFile *>
|
||||
createIRObjectFile(std::unique_ptr<MemoryBuffer> Object,
|
||||
LLVMContext &Context);
|
||||
static ErrorOr<IRObjectFile *> createIRObjectFile(MemoryBufferRef Object,
|
||||
LLVMContext &Context);
|
||||
};
|
||||
}
|
||||
}
|
||||
|
Reference in New Issue
Block a user