NetBSD re-synchronization of the source tree

This brings our tree to NetBSD 7.0, as found on -current on the
10-10-2015.

This updates:
 - LLVM to 3.6.1
 - GCC to GCC 5.1
 - Replace minix/commands/zdump with usr.bin/zdump
 - external/bsd/libelf has moved to /external/bsd/elftoolchain/
 - Import ctwm
 - Drop sprintf from libminc

Change-Id: I149836ac18e9326be9353958bab9b266efb056f0

external/gpl3/gcc/usr.bin/cpp/cpp.1

@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.23 (Pod::Simple 3.14)
+.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.20)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -124,7 +124,7 @@
 .\" ========================================================================
 .\"
 .IX Title "CPP 1"
-.TH CPP 1 "2011-06-23" "gcc-4.1.3" "GNU"
+.TH CPP 1 "2014-01-16" "gcc-4.8.3" "GNU"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -181,7 +181,8 @@ Standard C.  In its default mode, the \s-1GNU\s0 C preprocessor does not do a
 few things required by the standard.  These are features which are
 rarely, if ever, used, and may cause surprising changes to the meaning
 of a program which does not expect them.  To get strict \s-1ISO\s0 Standard C,
-you should use the \fB\-std=c89\fR or \fB\-std=c99\fR options, depending
+you should use the \fB\-std=c90\fR, \fB\-std=c99\fR or
+\&\fB\-std=c11\fR options, depending
 on which version of the standard you want.  To get all the mandatory
 diagnostics, you must also use \fB\-pedantic\fR.
 .PP
@@ -257,6 +258,8 @@ system include directory, the option is ignored to ensure that the
 default search order for system directories and the special treatment
 of system headers are not defeated
 \&.
+If \fIdir\fR begins with \f(CW\*(C`=\*(C'\fR, then the \f(CW\*(C`=\*(C'\fR will be replaced
+by the sysroot prefix; see \fB\-\-sysroot\fR and \fB\-isysroot\fR.
 .IP "\fB\-o\fR \fIfile\fR" 4
 .IX Item "-o file"
 Write output to \fIfile\fR.  This is the same as specifying \fIfile\fR
@@ -282,7 +285,6 @@ comment, or whenever a backslash-newline appears in a \fB//\fR comment.
 (Both forms have the same effect.)
 .IP "\fB\-Wtrigraphs\fR" 4
 .IX Item "-Wtrigraphs"
-\&\f(CW@anchor\fR{Wtrigraphs}
 Most trigraphs in comments cannot affect the meaning of the program.
 However, a trigraph that would form an escaped newline (\fB??/\fR at
 the end of a line) can, by changing where the comment begins or ends.
@@ -298,9 +300,6 @@ get trigraph conversion without warnings, but get the other
 Warn about certain constructs that behave differently in traditional and
 \&\s-1ISO\s0 C.  Also warn about \s-1ISO\s0 C constructs that have no traditional C
 equivalent, and problematic constructs which should be avoided.
-.IP "\fB\-Wimport\fR" 4
-.IX Item "-Wimport"
-Warn the first time \fB#import\fR is used.
 .IP "\fB\-Wundef\fR" 4
 .IX Item "-Wundef"
 Warn whenever an identifier which is not a macro is encountered in an
@@ -373,10 +372,11 @@ the included files, including those coming from \fB\-include\fR or
 \&\fB\-imacros\fR command line options.
 .Sp
 Unless specified explicitly (with \fB\-MT\fR or \fB\-MQ\fR), the
-object file name consists of the basename of the source file with any
-suffix replaced with object file suffix.  If there are many included
-files then the rule is split into several lines using \fB\e\fR\-newline.
-The rule has no commands.
+object file name consists of the name of the source file with any
+suffix replaced with object file suffix and with any leading directory
+parts removed.  If there are many included files then the rule is
+split into several lines using \fB\e\fR\-newline.  The rule has no
+commands.
 .Sp
 This option does not suppress the preprocessor's debug output, such as
 \&\fB\-dM\fR.  To avoid mixing such debug output with the dependency
@@ -397,8 +397,6 @@ This implies that the choice of angle brackets or double quotes in an
 \&\fB#include\fR directive does not in itself determine whether that
 header will appear in \fB\-MM\fR dependency output.  This is a
 slight change in semantics from \s-1GCC\s0 versions 3.0 and earlier.
-.Sp
-\&\f(CW@anchor\fR{dashMF}
 .IP "\fB\-MF\fR \fIfile\fR" 4
 .IX Item "-MF file"
 When used with \fB\-M\fR or \fB\-MM\fR, specifies a
@@ -436,9 +434,9 @@ This is typical output:
 .IP "\fB\-MT\fR \fItarget\fR" 4
 .IX Item "-MT target"
 Change the target of the rule emitted by dependency generation.  By
-default \s-1CPP\s0 takes the name of the main input file, including any path,
-deletes any file suffix such as \fB.c\fR, and appends the platform's
-usual object suffix.  The result is the target.
+default \s-1CPP\s0 takes the name of the main input file, deletes any
+directory components and any file suffix such as \fB.c\fR, and
+appends the platform's usual object suffix.  The result is the target.
 .Sp
 An \fB\-MT\fR option will set the target to be exactly the string you
 specify.  If you want multiple targets, you can specify them as a single
@@ -465,12 +463,12 @@ The default target is automatically quoted, as if it were given with
 \&\fB\-MD\fR is equivalent to \fB\-M \-MF\fR \fIfile\fR, except that
 \&\fB\-E\fR is not implied.  The driver determines \fIfile\fR based on
 whether an \fB\-o\fR option is given.  If it is, the driver uses its
-argument but with a suffix of \fI.d\fR, otherwise it take the
-basename of the input file and applies a \fI.d\fR suffix.
+argument but with a suffix of \fI.d\fR, otherwise it takes the name
+of the input file, removes any directory components and suffix, and
+applies a \fI.d\fR suffix.
 .Sp
 If \fB\-MD\fR is used in conjunction with \fB\-E\fR, any
-\&\fB\-o\fR switch is understood to specify the dependency output file
-(but \f(CW@pxref\fR{dashMF,,\-MF}), but if used without \fB\-E\fR, each \fB\-o\fR
+\&\fB\-o\fR switch is understood to specify the dependency output file, but if used without \fB\-E\fR, each \fB\-o\fR
 is understood to specify a target object file.
 .Sp
 Since \fB\-E\fR is not implied, \fB\-MD\fR can be used to generate
@@ -514,18 +512,21 @@ knows about C and \*(C+ standards; others may be added in the future.
 \&\fIstandard\fR
 may be one of:
 .RS 4
-.ie n .IP """iso9899:1990""" 4
-.el .IP "\f(CWiso9899:1990\fR" 4
-.IX Item "iso9899:1990"
+.ie n .IP """c90""" 4
+.el .IP "\f(CWc90\fR" 4
+.IX Item "c90"
 .PD 0
 .ie n .IP """c89""" 4
 .el .IP "\f(CWc89\fR" 4
 .IX Item "c89"
+.ie n .IP """iso9899:1990""" 4
+.el .IP "\f(CWiso9899:1990\fR" 4
+.IX Item "iso9899:1990"
 .PD
-The \s-1ISO\s0 C standard from 1990.  \fBc89\fR is the customary shorthand for
+The \s-1ISO\s0 C standard from 1990.  \fBc90\fR is the customary shorthand for
 this version of the standard.
 .Sp
-The \fB\-ansi\fR option is equivalent to \fB\-std=c89\fR.
+The \fB\-ansi\fR option is equivalent to \fB\-std=c90\fR.
 .ie n .IP """iso9899:199409""" 4
 .el .IP "\f(CWiso9899:199409\fR" 4
 .IX Item "iso9899:199409"
@@ -546,9 +547,27 @@ The 1990 C standard, as amended in 1994.
 .PD
 The revised \s-1ISO\s0 C standard, published in December 1999.  Before
 publication, this was known as C9X.
+.ie n .IP """iso9899:2011""" 4
+.el .IP "\f(CWiso9899:2011\fR" 4
+.IX Item "iso9899:2011"
+.PD 0
+.ie n .IP """c11""" 4
+.el .IP "\f(CWc11\fR" 4
+.IX Item "c11"
+.ie n .IP """c1x""" 4
+.el .IP "\f(CWc1x\fR" 4
+.IX Item "c1x"
+.PD
+The revised \s-1ISO\s0 C standard, published in December 2011.  Before
+publication, this was known as C1X.
+.ie n .IP """gnu90""" 4
+.el .IP "\f(CWgnu90\fR" 4
+.IX Item "gnu90"
+.PD 0
 .ie n .IP """gnu89""" 4
 .el .IP "\f(CWgnu89\fR" 4
 .IX Item "gnu89"
+.PD
 The 1990 C standard plus \s-1GNU\s0 extensions.  This is the default.
 .ie n .IP """gnu99""" 4
 .el .IP "\f(CWgnu99\fR" 4
@@ -559,6 +578,15 @@ The 1990 C standard plus \s-1GNU\s0 extensions.  This is the default.
 .IX Item "gnu9x"
 .PD
 The 1999 C standard plus \s-1GNU\s0 extensions.
+.ie n .IP """gnu11""" 4
+.el .IP "\f(CWgnu11\fR" 4
+.IX Item "gnu11"
+.PD 0
+.ie n .IP """gnu1x""" 4
+.el .IP "\f(CWgnu1x\fR" 4
+.IX Item "gnu1x"
+.PD
+The 2011 C standard plus \s-1GNU\s0 extensions.
 .ie n .IP """c++98""" 4
 .el .IP "\f(CWc++98\fR" 4
 .IX Item "c++98"
@@ -619,6 +647,8 @@ specified by \fB\-include\fR.
 Search \fIdir\fR for header files, but do it \fIafter\fR all
 directories specified with \fB\-I\fR and the standard system directories
 have been exhausted.  \fIdir\fR is treated as a system include directory.
+If \fIdir\fR begins with \f(CW\*(C`=\*(C'\fR, then the \f(CW\*(C`=\*(C'\fR will be replaced
+by the sysroot prefix; see \fB\-\-sysroot\fR and \fB\-isysroot\fR.
 .IP "\fB\-iprefix\fR \fIprefix\fR" 4
 .IX Item "-iprefix prefix"
 Specify \fIprefix\fR as the prefix for subsequent \fB\-iwithprefix\fR
@@ -637,13 +667,22 @@ would; \fB\-iwithprefix\fR puts it where \fB\-idirafter\fR would.
 .IP "\fB\-isysroot\fR \fIdir\fR" 4
 .IX Item "-isysroot dir"
 This option is like the \fB\-\-sysroot\fR option, but applies only to
-header files.  See the \fB\-\-sysroot\fR option for more information.
+header files (except for Darwin targets, where it applies to both header
+files and libraries).  See the \fB\-\-sysroot\fR option for more
+information.
+.IP "\fB\-imultilib\fR \fIdir\fR" 4
+.IX Item "-imultilib dir"
+Use \fIdir\fR as a subdirectory of the directory containing
+target-specific \*(C+ headers.
 .IP "\fB\-isystem\fR \fIdir\fR" 4
 .IX Item "-isystem dir"
 Search \fIdir\fR for header files, after all directories specified by
 \&\fB\-I\fR but before the standard system directories.  Mark it
 as a system directory, so that it gets the same special treatment as
 is applied to the standard system directories.
+.Sp
+If \fIdir\fR begins with \f(CW\*(C`=\*(C'\fR, then the \f(CW\*(C`=\*(C'\fR will be replaced
+by the sysroot prefix; see \fB\-\-sysroot\fR and \fB\-isysroot\fR.
 .IP "\fB\-cxx\-isystem\fR \fIdir\fR" 4
 .IX Item "-cxx-isystem dir"
 Search \fIdir\fR for \*(C+ header files, after all directories specified by
@@ -656,6 +695,30 @@ Search \fIdir\fR only for header files requested with
 \&\f(CW\*(C`#include\ "\f(CIfile\f(CW"\*(C'\fR; they are not searched for
 \&\f(CW\*(C`#include\ <\f(CIfile\f(CW>\*(C'\fR, before all directories specified by
 \&\fB\-I\fR and before the standard system directories.
+.Sp
+If \fIdir\fR begins with \f(CW\*(C`=\*(C'\fR, then the \f(CW\*(C`=\*(C'\fR will be replaced
+by the sysroot prefix; see \fB\-\-sysroot\fR and \fB\-isysroot\fR.
+.IP "\fB\-fdirectives\-only\fR" 4
+.IX Item "-fdirectives-only"
+When preprocessing, handle directives, but do not expand macros.
+.Sp
+The option's behavior depends on the \fB\-E\fR and \fB\-fpreprocessed\fR
+options.
+.Sp
+With \fB\-E\fR, preprocessing is limited to the handling of directives
+such as \f(CW\*(C`#define\*(C'\fR, \f(CW\*(C`#ifdef\*(C'\fR, and \f(CW\*(C`#error\*(C'\fR.  Other
+preprocessor operations, such as macro expansion and trigraph
+conversion are not performed.  In addition, the \fB\-dD\fR option is
+implicitly enabled.
+.Sp
+With \fB\-fpreprocessed\fR, predefinition of command line and most
+builtin macros is disabled.  Macros such as \f(CW\*(C`_\|_LINE_\|_\*(C'\fR, which are
+contextually dependent, are handled normally.  This enables compilation of
+files previously preprocessed with \f(CW\*(C`\-E \-fdirectives\-only\*(C'\fR.
+.Sp
+With both \fB\-E\fR and \fB\-fpreprocessed\fR, the rules for
+\&\fB\-fpreprocessed\fR take precedence.  This enables full preprocessing of
+files previously preprocessed with \f(CW\*(C`\-E \-fdirectives\-only\*(C'\fR.
 .IP "\fB\-iremap\fR \fIsrc\fR\fB:\fR\fIdst\fR" 4
 .IX Item "-iremap src:dst"
 Replace the prefix \fIsrc\fR in _\|_FILE_\|_ with \fIdst\fR at expansion time.
@@ -663,13 +726,15 @@ This option can be specified more than once.  Processing stops at the first
 match.
 .IP "\fB\-fdollars\-in\-identifiers\fR" 4
 .IX Item "-fdollars-in-identifiers"
-\&\f(CW@anchor\fR{fdollars\-in\-identifiers}
 Accept \fB$\fR in identifiers.
 .IP "\fB\-fextended\-identifiers\fR" 4
 .IX Item "-fextended-identifiers"
 Accept universal character names in identifiers.  This option is
 experimental; in a future version of \s-1GCC\s0, it will be enabled by
 default for C99 and \*(C+.
+.IP "\fB\-fno\-canonical\-system\-headers\fR" 4
+.IX Item "-fno-canonical-system-headers"
+When preprocessing, do not shorten system header paths with canonicalization.
 .IP "\fB\-fpreprocessed\fR" 4
 .IX Item "-fpreprocessed"
 Indicate to the preprocessor that the input file has already been
@@ -690,6 +755,38 @@ Set the distance between tab stops.  This helps the preprocessor report
 correct column numbers in warnings or errors, even if tabs appear on the
 line.  If the value is less than 1 or greater than 100, the option is
 ignored.  The default is 8.
+.IP "\fB\-fdebug\-cpp\fR" 4
+.IX Item "-fdebug-cpp"
+This option is only useful for debugging \s-1GCC\s0.  When used with
+\&\fB\-E\fR, dumps debugging information about location maps.  Every
+token in the output is preceded by the dump of the map its location
+belongs to.  The dump of the map holding the location of a token would
+be:
+.Sp
+.Vb 1
+\&        {"P":F</file/path>;"F":F</includer/path>;"L":<line_num>;"C":<col_num>;"S":<system_header_p>;"M":<map_address>;"E":<macro_expansion_p>,"loc":<location>}
+.Ve
+.Sp
+When used without \fB\-E\fR, this option has no effect.
+.IP "\fB\-ftrack\-macro\-expansion\fR[\fB=\fR\fIlevel\fR]" 4
+.IX Item "-ftrack-macro-expansion[=level]"
+Track locations of tokens across macro expansions. This allows the
+compiler to emit diagnostic about the current macro expansion stack
+when a compilation error occurs in a macro expansion. Using this
+option makes the preprocessor and the compiler consume more
+memory. The \fIlevel\fR parameter can be used to choose the level of
+precision of token location tracking thus decreasing the memory
+consumption if necessary. Value \fB0\fR of \fIlevel\fR de-activates
+this option just as if no \fB\-ftrack\-macro\-expansion\fR was present
+on the command line. Value \fB1\fR tracks tokens locations in a
+degraded mode for the sake of minimal memory overhead. In this mode
+all tokens resulting from the expansion of an argument of a
+function-like macro have the same location. Value \fB2\fR tracks
+tokens locations completely. This value is the most memory hungry.
+When this option is given no argument, the default parameter value is
+\&\fB2\fR.
+.Sp
+Note that \-ftrack\-macro\-expansion=2 is activated by default.
 .IP "\fB\-fexec\-charset=\fR\fIcharset\fR" 4
 .IX Item "-fexec-charset=charset"
 Set the execution character set, used for string and character
@@ -762,6 +859,9 @@ Assuming you have no file \fIfoo.h\fR, the command
 .Ve
 .Sp
 will show all the predefined macros.
+.Sp
+If you use \fB\-dM\fR without the \fB\-E\fR option, \fB\-dM\fR is
+interpreted as a synonym for \fB\-fdump\-rtl\-mach\fR.
 .IP "\fBD\fR" 4
 .IX Item "D"
 Like \fBM\fR except in two respects: it does \fInot\fR include the
@@ -775,6 +875,13 @@ Like \fBD\fR, but emit only the macro names, not their expansions.
 .IX Item "I"
 Output \fB#include\fR directives in addition to the result of
 preprocessing.
+.IP "\fBU\fR" 4
+.IX Item "U"
+Like \fBD\fR except that only macros that are expanded, or whose
+definedness is tested in preprocessor directives, are output; the
+output is delayed until the use or test of the macro; and
+\&\fB#undef\fR directives are also output for macros tested but
+undefined at the time.
 .RE
 .RS 4
 .RE
@@ -922,12 +1029,10 @@ always done if the found file is a directory).
 \&\fIbinutils\fR.
 .SH "COPYRIGHT"
 .IX Header "COPYRIGHT"
-Copyright (c) 1987, 1989, 1991, 1992, 1993, 1994, 1995, 1996,
-1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
-Free Software Foundation, Inc.
+Copyright (c) 1987\-2013 Free Software Foundation, Inc.
 .PP
 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
+under the terms of the \s-1GNU\s0 Free Documentation License, Version 1.3 or
 any later version published by the Free Software Foundation.  A copy of
 the license is included in the
 man page \fIgfdl\fR\|(7).