COFF: Update README.

Avoid saying this is based on sections because it's not very accurate.
That we don't split section into smaller chunks of data does not mean
that the linker is built on top of that.
In reality, most part of the code do not care about underlying data,
so they are neither based on "atoms" nor sections.
The symbol table only cares about symbol names and their types.
The writer handles list of chunks, which look like just blobs,
and the writer doesn't care what those chunks are backed by.
The only thing that interact with sections is SectionChunk, which is
abstracted away as one type of Chunk.

llvm-svn: 238902

1 files changed, 5 insertions, 5 deletions

diff --git a/lld/COFF/README.md b/lld/COFF/README.md
index 3d0c6e4fe62..43dca2ca81e 100644
--- a/lld/COFF/README.md
+++ b/lld/COFF/README.md
@@ -6,11 +6,11 @@ format. Because the fundamental design of this port is different from
 the other ports of LLD, this port is separated to this directory.
 
 The other ports are based on the Atom model, in which symbols and
-references are represented as vertices and edges of graphs. The port
-in this directory is based on sections instead. The aim is
-simplicity and better performance. Our plan is to implement a linker
-for the PE/COFF format based on a different idea, and then apply the
-same idea to the ELF if proved to be effective.
+references are represented as vertices and edges of graphs.
+We don't use that model to aim for performance and simplicity.
+Our plan is to implement a linker for the PE/COFF format based on a
+different idea, and then apply the same idea to the ELF if proved to
+be effective.
 
 Overall Design
 --------------