[llvm] c2b3a9a - [Docs] Update opaque pointers transition state (NFC)

[Nikita Popov via llvm-commits]

Author: Nikita Popov
Date: 2022-03-24T11:51:54+01:00
New Revision: c2b3a9abc89dd0b032e196c1942e1bca41960663

URL: https://github.com/llvm/llvm-project/commit/c2b3a9abc89dd0b032e196c1942e1bca41960663
DIFF: https://github.com/llvm/llvm-project/commit/c2b3a9abc89dd0b032e196c1942e1bca41960663.diff

LOG: [Docs] Update opaque pointers transition state (NFC)

Opaque pointer support in Clang is now complete.

Added: 
    

Modified: 
    llvm/docs/OpaquePointers.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/OpaquePointers.rst b/llvm/docs/OpaquePointers.rst
index 8459784b41caf..b13a82895edb3 100644
--- a/llvm/docs/OpaquePointers.rst
+++ b/llvm/docs/OpaquePointers.rst
@@ -66,8 +66,8 @@ mode (currently still the default) all pointer types have a pointee type and
 opaque pointers cannot be used. In opaque pointers mode, all pointers are
 opaque. The opaque pointer mode can be enabled using ``-opaque-pointers`` in
 LLVM tools like ``opt``, or ``-mllvm -opaque-pointers`` in clang. Additionally,
-opaque pointer mode is automatically enabled for IR files that use the ``ptr``
-type.
+opaque pointer mode is automatically enabled for IR and bitcode files that use
+the ``ptr`` type.
 
 In opaque pointer mode, all typed pointers used in IR, bitcode, or created
 using ``PointerType::get()`` and similar APIs are automatically converted into
@@ -199,10 +199,6 @@ to build most C and C++ code in opaque pointer mode, both with and without
 optimization, and produce working binaries. However, thes are still some
 open problems:
 
-* While clang mostly supports opaque pointers, additional effort will be
-  needed to systematically remove all uses of the deprecated
-  ``Address::deprecated()`` constructor.
-
 * We do not yet have a firm strategy for enabling opaque pointers. A large
   number of tests will have to be migrated to use opaque pointers.