diff options
author | Joerg Sonnenberger <joerg@bec.de> | 2013-09-07 18:01:39 +0000 |
---|---|---|
committer | Joerg Sonnenberger <joerg@bec.de> | 2013-09-07 18:01:39 +0000 |
commit | a82566b86e511f018fa7eadf11092e01f4cc5cf6 (patch) | |
tree | 03a75a43ccf6c57aeba61cd6f8bcfec80fcd6038 /lld/docs/Readers.rst | |
parent | 0310e734c3acf88eaef69808e39c77cb2066ade7 (diff) | |
download | bcm5719-llvm-a82566b86e511f018fa7eadf11092e01f4cc5cf6.tar.gz bcm5719-llvm-a82566b86e511f018fa7eadf11092e01f4cc5cf6.zip |
Update documentation.
llvm-svn: 190255
Diffstat (limited to 'lld/docs/Readers.rst')
-rw-r--r-- | lld/docs/Readers.rst | 8 |
1 files changed, 1 insertions, 7 deletions
diff --git a/lld/docs/Readers.rst b/lld/docs/Readers.rst index d61534bd137..ddda4736f49 100644 --- a/lld/docs/Readers.rst +++ b/lld/docs/Readers.rst @@ -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. |