From c2b3a9abc89dd0b032e196c1942e1bca41960663 Mon Sep 17 00:00:00 2001 From: Nikita Popov Date: Thu, 24 Mar 2022 11:51:04 +0100 Subject: [PATCH] [Docs] Update opaque pointers transition state (NFC) Opaque pointer support in Clang is now complete. --- llvm/docs/OpaquePointers.rst | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/llvm/docs/OpaquePointers.rst b/llvm/docs/OpaquePointers.rst index 8459784b41ca..b13a82895edb 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.