You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
to represent either a version of a function (eg, parameter 3 is the constant x) or a piece of a function (eg, coroutine resumption slice of a function) or similar. However, demanglers are inconsistent in their handling of this form -- some require the suffix to contain only digits, others support and ignore an arbitrary suffix, others simply reject all such names as being an invalid mangling.
We should officially permit such manglings for internal-linkage symbols, with an arbitrary suffix, in order to give clear guidance to demangler implementers.
The text was updated successfully, but these errors were encountered:
…f using a period-separated suffix for symbol variants.
The intent is to provide a mechanism whereby implementations can provide
multiple definitions of a symbol (eg, a constant-propagated version of a
function, the residual after partial inlining or dead argument
elimination, a resumption function for a coroutine, ...) that are named
after the original in backtraces, debuggers, and so on.
Fixesitanium-cxx-abi#35.
Several vendors use mangled names of the form
real_mangled_name.suffix
to represent either a version of a function (eg, parameter 3 is the constant x) or a piece of a function (eg, coroutine resumption slice of a function) or similar. However, demanglers are inconsistent in their handling of this form -- some require the suffix to contain only digits, others support and ignore an arbitrary suffix, others simply reject all such names as being an invalid mangling.
We should officially permit such manglings for internal-linkage symbols, with an arbitrary suffix, in order to give clear guidance to demangler implementers.
The text was updated successfully, but these errors were encountered: