[lld] r190255 - Update documentation.

[Joerg Sonnenberger]

Author: joerg
Date: Sat Sep  7 13:01:39 2013
New Revision: 190255

URL: http://llvm.org/viewvc/llvm-project?rev=190255&view=rev
Log:
Update documentation.

Modified:
    lld/trunk/docs/Readers.rst

Modified: lld/trunk/docs/Readers.rst
URL: http://llvm.org/viewvc/llvm-project/lld/trunk/docs/Readers.rst?rev=190255&r1=190254&r2=190255&view=diff
==============================================================================
--- lld/trunk/docs/Readers.rst (original)
+++ lld/trunk/docs/Readers.rst Sat Sep  7 13:01:39 2013
@@ -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
 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.