Update documentation.

llvm-svn: 190255
This commit is contained in:
Joerg Sonnenberger 2013-09-07 18:01:39 +00:00
parent 0310e734c3
commit a82566b86e
1 changed files with 1 additions and 7 deletions

View File

@ -74,7 +74,7 @@ some temporary object.
The key method to implement in a reader is::
virtual error_code parseFile(std::unique_ptr<MemoryBuffer> mb,
virtual error_code parseFile(LinkerInput &input,
std::vector<std::unique_ptr<File>> &result);
It takes a memory buffer (which contains the contents of the object file
@ -87,12 +87,6 @@ simple a File pointer) because some file formats allow multiple object
Memory Ownership
----------------
If parseFile() is successful, it either passes ownership of the MemoryBuffer
to the File object, or it deletes the MemoryBuffer. The former is done if the
Atoms contain pointers into the MemoryBuffer (e.g. StringRefs for symbols
or ArrayRefs for section content). If parseFile() fails, the MemoryBuffer
must be deleted by the Reader.
Atoms are always owned by their File object. During core linking when Atoms
are coalesced or stripped away, core linking does not delete them.
Core linking just removes those unused Atoms from its internal list.