maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[Docs] Update opaque pointers transition state (NFC) 

Opaque pointer support in Clang is now complete.
This commit is contained in:
Nikita Popov 2022-03-24 11:51:04 +01:00
parent c34365149d
commit c2b3a9abc8
1 changed files with 2 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
llvm/docs/OpaquePointers.rst
View File

@ -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.