@@ -8673,21 +8673,21 @@ denoting if the type contains a pointer.
86738673'``ref``' Metadata
86748674^^^^^^^^^^^^^^^^^^
86758675
8676- The ``ref`` metadata may be attached to a global variable definition with a
8677- single argument that references a global object. The metadata is lowered to a
8678- .ref directive which will emit a relocation introducing an explicit dependence
8679- to the referenced symbol. This is typically used when there is some implicit
8680- dependence between the symbols that is otherwise opaque to the linker. One such
8681- example is metadata which is accessed by a runtime with associated
8682- ``__start_<section_name>`` and ``__stop_<section_name>`` symbols.
8676+ The ``ref`` metadata may be attached to a function or global variable
8677+ definition with a single argument that references a global object.
8678+ This is typically used when there is some implicit dependence between the
8679+ symbols that is otherwise opaque to the linker. One such example is metadata
8680+ which is accessed by a runtime with associated ``__start_<section_name>`` and
8681+ ``__stop_<section_name>`` symbols.
8682+
8683+ It does not have any effect on non-XCOFF targets.
86838684
86848685This metadata lowers to the .ref assembly directive which will add a relocation
86858686representing an implicit reference from the section the global belongs to, to
8686- the associated symbol. This link will keep the associated symbol alive if the
8687- section is not garbage collected. More than one associated node can be attached
8688- to the same global variable.
8687+ the associated symbol. This link will keep the referenced symbol alive if the
8688+ section is not garbage collected. More than one ref node can be attached
8689+ to the same function or global variable.
86898690
8690- It does not have any effect on non-XCOFF targets.
86918691
86928692Example:
86938693
0 commit comments