OpenGrok

Automatically generated by Pod::Man v1.37, Pod::Parser v1.32

Standard preamble:
========================================================================

\\$1

.. ..

..

.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' 'br\}
If the F register is turned on, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.
. de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . nr % 0 . rr F .\}
For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.

Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "C++FILT 1" c++filt - Demangle C++ and Java symbols. Header "SYNOPSIS" c++filt [-_|--strip-underscores] [-n|--no-strip-underscores] [-p|--no-params] [-t|--types] [-i|--no-verbose] [-s format|--format=format] [--help] [--version] [symbol...] Header "DESCRIPTION" The \*(C+ and Java languages provide function overloading, which means that you can write many functions with the same name, providing that each function takes parameters of different types. In order to be able to distinguish these similarly named functions \*(C+ and Java encode them into a low-level assembler name which uniquely identifies each different version. This process is known as mangling. The \fBc++filt [1] program does the inverse mapping: it decodes (demangles) low-level names into user-level names so that they can be read.

Every alphanumeric word (consisting of letters, digits, underscores, dollars, or periods) seen in the input is a potential mangled name. If the name decodes into a \*(C+ name, the \*(C+ name replaces the low-level name in the output, otherwise the original word is output. In this way you can pass an entire assembler source file, containing mangled names, through c++filt and see the same source file containing demangled names.

You can also use c++filt to decipher individual symbols by passing them on the command line:

.Vb 1 c++filt <symbol> .Ve

If no symbol arguments are given, c++filt reads symbol names from the standard input instead. All the results are printed on the standard output. The difference between reading names from the command line versus reading names from the standard input is that command line arguments are expected to be just mangled names and no checking is performed to seperate them from surrounding text. Thus for example:

.Vb 1 c++filt -n _Z1fv .Ve

will work and demangle the name to \*(L"f()\*(R" whereas:

.Vb 1 c++filt -n _Z1fv, .Ve

will not work. (Note the extra comma at the end of the mangled name which makes it invalid). This command however will work:

.Vb 1 echo _Z1fv, | c++filt -n .Ve

and will display \*(L"f(),\*(R" ie the demangled name followed by a trailing comma. This behaviour is because when the names are read from the standard input it is expected that they might be part of an assembler source file where there might be extra, extraneous characters trailing after a mangled name. eg:

.Vb 1 .type _Z1fv, @function .Ve

Header "OPTIONS" Item "-_"

0

Item "--strip-underscores"

On some systems, both the C and \*(C+ compilers put an underscore in front of every name. For example, the C name \*(C`foo\*(C' gets the low-level name \*(C`_foo\*(C'. This option removes the initial underscore. Whether \fBc++filt removes the underscore by default is target dependent.

Item "-j"

0

Item "--java"

Prints demangled names using Java syntax. The default is to use \*(C+ syntax.

Item "-n"

0

Item "--no-strip-underscores"

Do not remove the initial underscore.

Item "-p"

0

Item "--no-params"

When demangling the name of a function, do not display the types of the function's parameters.

Item "-t"

0

Item "--types"

Attempt to demangle types as well as function names. This is disabled by default since mangled types are normally only used internally in the compiler, and they can be confused with non-mangled names. eg a function called \*(L"a\*(R" treated as a mangled type name would be demangled to \*(L"signed char\*(R".

Item "-i"

0

Item "--no-verbose"

Do not include implementation details (if any) in the demangled output.

Item "-s format"

0

Item "--format=format"

\fBc++filt can decode various methods of mangling, used by different compilers. The argument to this option selects which method it uses: Item "auto" Automatic selection based on executable (the default method) Item "gnu" the one used by the \s-1GNU\s0 \*(C+ compiler (g++) Item "lucid" the one used by the Lucid compiler (lcc) Item "arm" the one specified by the \*(C+ Annotated Reference Manual Item "hp" the one used by the \s-1HP\s0 compiler (aCC) Item "edg" the one used by the \s-1EDG\s0 compiler Item "gnu-v3" the one used by the \s-1GNU\s0 \*(C+ compiler (g++) with the V3 \s-1ABI\s0. Item "java" the one used by the \s-1GNU\s0 Java compiler (gcj) Item "gnat" the one used by the \s-1GNU\s0 Ada compiler (\s-1GNAT\s0).

Item "--help" Print a summary of the options to c++filt and exit. Item "--version" Print the version number of c++filt and exit. Item "@file" Read command-line options from file. The options read are inserted in place of the original @file option. If file does not exist, or cannot be read, then the option will be treated literally, and not removed. .Sp Options in file are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The file may itself contain additional @file options; any such options will be processed recursively. Header "FOOTNOTES" MS-DOS does not allow \*(C`+\*(C' characters in file names, so on MS-DOS this program is named \s-1CXXFILT\s0. Header "SEE ALSO" the Info entries for binutils. Header "COPYRIGHT" Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled \*(L"\s-1GNU\s0 Free Documentation License\*(R".