[libc] Add a README to the sub-directories under the utils directory.

[sivachandra]

Summary

Also, the source layout document has been updated to reflect the current
layout of the utils directory.

[PaulkaToast]

libc/utils/CPP/README.md

1–6

"This directory contains re-implementations of some C++ standard library utilities" or "This directory contains a re-implementation of some of the C++ standard library"

libc/utils/UnitTest/README.md

23

"extend" instead of "extended"

[sivachandra]

Address comments.

[PaulkaToast]

libc/utils/CPP/README.md

1–6

I think you missed this one?

[sivachandra]

Add a missed word.

[sivachandra]

libc/utils/CPP/README.md

1–6

Ah, you wanted an additional "utilities".

[MaskRay]

libc/utils/HdrGen/README.md

7

Delete the trailing empty line.

libc/docs/source_layout.rst

 LLVM-libc Source Tree Layout
 ============================
 
 At the top-level, LLVM-libc source tree is organized in to the following
 directories::
 
    + libc
         - cmake
         - docs
         - fuzzing
         - include
         - lib
         - loader
         - src
         - test
-        + utils
-            - build_scripts
-            - testing
+        - utils
         - www
 
 Each of these directories is explained in detail below.
 
 The ``cmake`` directory
 -----------------------
 
 The ``cmake`` directory contains the implementations of LLVM-libc's CMake build

 ----------------------
 
 This directory contains tests for the various components of llvm-libc. The
 directory structure within this directory mirrors the directory structure of the
 toplevel ``libc`` directory itself. A test for, say the ``mmap`` function, lives
 in the directory ``test/src/sys/mman/`` as implementation of ``mmap`` lives in
 ``src/sys/mman``.
 
-The ``www`` directory
+The `utils` directory
 ---------------------
 
-The ``www`` directory contains the HTML content of libc.llvm.org
-
-The ``utils/build_scripts`` directory
--------------------------------------
+This directory contains utilities used by other parts of the llvm-libc system.
+See the `README` files, in the sub-directories within this directory, to learn
+about the various utilities.
 
-This directory contains scripts which support the build system, tooling etc.
+The ``www`` directory
+---------------------
 
-The ``utils/testing`` directory
--------------------------------
+The ``www`` directory contains the HTML content of libc.llvm.org
 
-This directory contains testing infrastructure.

libc/utils/CPP/README.md

-This directory contains re-implementations of some C++ standard library as well
-as some LLVM utilities. These are to be used with internal LLVM libc code and
-tests. More utilities will be added on an as needed basis. There are certain
-rules to be followed for future changes and additions:
+This directory contains re-implementations of some C++ standard library, as
+well as some LLVM utilities. These utilities are for use with internal LLVM libc
+code and tests.
+
+More utilities will be added on an as needed basis. There are certain rules to
+be followed for future changes and additions:
 
 1. Only two kind of headers can be included: Other headers from this directory,
 and free standing C headers.
 2. Free standing C headers are to be included as C headers and not as C++
 headers. That is, use `#include <stddef.h>` and not `#include <cstddef>`.
 3. The utilities should be defined in the namespace `__llvm_libc::cpp`. The
 higher level namespace should have a `__` prefix to avoid symbol name pollution
 when the utilities are used in implementation of public functions.

libc/utils/HdrGen/README.md

+# The LLVM libc header generation system
+
+LLVM libc uses a header generation scheme to generate public as well as internal
+header files. This directory contains the implementation of the header generator
+which drives this header generation scheme.
+

libc/utils/UnitTest/README.md

+# The LLVM libc unit test framework
+
+This directory contains a lightweight implementation of a
+[gtest](https://github.com/google/googletest) like unit test framework for LLVM
+libc.
+
+## Why not gtest?
+
+While gtest is great, featureful and time tested, it uses the C and C++
+standard libraries. Hence, using it to test LLVM libc (which is also an
+implementation of the C standard libraries) causes various kinds of
+mixup/conflict problems.
+
+## How is it different from gtest?
+
+LLVM libc's unit test framework is much less featureful as compared to gtest.
+But, what is available strives to be exactly like gtest.
+
+## Will it be made as featurful as gtest in future?
+
+It is not clear if LLVM libc needs/will need every feature of gtest. We only
+intend to extend it on an _as needed_ basis. Hence, it might never be as
+featureful as gtest.