FreeChainXenon/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

cp-tree.h (DECL_NONSTATIC_MEMBER_FUNCTION_P): New macro.

Browse source 
* cp-tree.h (DECL_NONSTATIC_MEMBER_FUNCTION_P): New macro.
	(revert_static_member_fn): Declare.
	* decl.c (revert_static_member_fn): Remove declaration.  Change
	linkage from internal to external.
	(cp_finish_decl): Deal with virtual functions in classes local to
	template functions.
	* decl2.c (finish_file): Don't forget to emit increment/decrement
	expressions in initializers for file-scope variables.
	* parse.y (typename_sub2): If the typename doesn't names a
	template, rather than a type, issue an error message.
	* pt.c (check_explicit_specialization): Handle specializations of
	static member functions.
	(coerce_template_parms): Handle offset references to lists of
	member functions.
	* search.c (note_debug_info_needed): Don't crash when handed a
	type which is being defined.
	* typeck.c (complete_type): Don't crash when handed NULL_TREE;
	that can happen with some illegal code.

From-SVN: r17598
This commit is contained in:
Mark Mitchell 1998-02-02 11:41:39 +00:00 • committed by Jason Merrill
parent 318e3b20e4
commit 8857f91e00
10 changed files with 581 additions and 439 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
gcc/cp/ChangeLog
View file

@ -1,3 +1,24 @@
Mon Feb 2 11:24:22 1998 Mark Mitchell <mmitchell@usa.net>
* cp-tree.h (DECL_NONSTATIC_MEMBER_FUNCTION_P): New macro.
(revert_static_member_fn): Declare.
* decl.c (revert_static_member_fn): Remove declaration. Change
linkage from internal to external.
(cp_finish_decl): Deal with virtual functions in classes local to
template functions.
* decl2.c (finish_file): Don't forget to emit increment/decrement
expressions in initializers for file-scope variables.
* parse.y (typename_sub2): If the typename doesn't names a
template, rather than a type, issue an error message.
* pt.c (check_explicit_specialization): Handle specializations of
static member functions.
(coerce_template_parms): Handle offset references to lists of
member functions.
* search.c (note_debug_info_needed): Don't crash when handed a
type which is being defined.
* typeck.c (complete_type): Don't crash when handed NULL_TREE;
that can happen with some illegal code.
Mon Feb 2 00:57:38 1998 Kaveh R. Ghazi <ghazi@caip.rutgers.edu>
* call.c (user_harshness): Initialize `code' to 0.

8
gcc/cp/cp-tree.h
View file

@ -1020,10 +1020,15 @@ struct lang_decl
(TREE_CODE (NODE) == VAR_DECL || TREE_CODE (NODE) == TYPE_DECL \
|| TREE_CODE (NODE) == CONST_DECL)
/* Nonzero for FUNCTION_DECL means that this decl is a non-static
member function. */
#define DECL_NONSTATIC_MEMBER_FUNCTION_P(NODE) \
(TREE_CODE (TREE_TYPE (NODE)) == METHOD_TYPE)
/* Nonzero for FUNCTION_DECL means that this decl is a member function
(static or non-static). */
#define DECL_FUNCTION_MEMBER_P(NODE) \
(TREE_CODE (TREE_TYPE (NODE)) == METHOD_TYPE || DECL_STATIC_FUNCTION_P (NODE))
(DECL_NONSTATIC_MEMBER_FUNCTION_P (NODE) || DECL_STATIC_FUNCTION_P (NODE))
/* Nonzero for FUNCTION_DECL means that this member function
has `this' as const X *const. */
@ -2119,6 +2124,7 @@ extern int in_function_p PROTO((void));
extern void replace_defarg PROTO((tree, tree));
extern void print_other_binding_stack PROTO((struct binding_level *));
extern tree strip_attrs PROTO((tree));
extern void revert_static_member_fn PROTO((tree*, tree*, tree*));
/* in decl2.c */
extern int flag_assume_nonnull_objects;

9
gcc/cp/decl.c
View file

@ -136,7 +136,6 @@ static struct stack_level *decl_stack;
static tree grokparms PROTO((tree, int));
static tree lookup_nested_type PROTO((tree, tree));
static char *redeclaration_error_message PROTO((tree, tree));
static void revert_static_member_fn PROTO((tree *, tree *, tree *));
static tree push_overloaded_decl PROTO((tree, int));
static void push_overloaded_decl_top_level PROTO((tree, int));
@ -6484,8 +6483,10 @@ cp_finish_decl (decl, init, asmspec_tree, need_pop, flags)
{
tree stmt = DECL_VINDEX (decl);
/* If the decl is declaring a member of a local class (in a
template function), there will be no associated stmt. */
if (stmt != NULL_TREE)
template function), the DECL_VINDEX will either be NULL,
or it will be an actual virtual function index, not a
DECL_STMT. */
if (stmt != NULL_TREE && TREE_CODE (stmt) == DECL_STMT)
{
DECL_VINDEX (decl) = NULL_TREE;
TREE_OPERAND (stmt, 2) = copy_to_permanent (init);
@ -12997,7 +12998,7 @@ finish_stmt ()
(TREE_TYPE (decl)) to ARGTYPES, as doing so will corrupt the types of
other decls. Either pass the addresses of local variables or NULL. */
static void
void
revert_static_member_fn (decl, fn, argtypes)
tree *decl, *fn, *argtypes;
{

4
gcc/cp/decl2.c
View file

@ -3140,6 +3140,10 @@ finish_file ()
}
else
expand_assignment (decl, init, 0, 0);
/* The expression might have involved increments and
decrements. */
emit_queue ();
/* Cleanup any temporaries needed for the initial value. */
expand_end_target_temps ();

486
gcc/cp/g++FAQ.texi
View file

@ -3,7 +3,7 @@
@setfilename g++FAQ.info
@settitle Frequently asked questions about the GNU C++ compiler
@setchapternewpage off
@c version: @(#)g++FAQ.texi 1.57 12/14/97
@c version: @(#)g++FAQ.texi 1.60 01/31/98
@c %**end of header
@iftex
@ -12,7 +12,7 @@
@titlepage
@title G++ FAQ
@subtitle Frequently asked questions about the GNU C++ compiler
@subtitle December 14, 1997
@subtitle January 31, 1998
@sp 1
@author Joe Buck
@page
@ -35,8 +35,9 @@ all those who sent suggestions for improvements. Thanks to Marcus Speh
for doing the index. A hypertext version is available on the World Wide
Web at @file{http://www.cygnus.com/misc/g++FAQ_toc.html}.
@strong{News flash}: egcs has been released, and the 2.8.0 release is
expected very soon!
@strong{News flash}: gcc 2.8.0 has finally been released!
This FAQ still has much material that refers to older releases; it will
take some time before it is completely "modernized".
Please send updates and corrections to the FAQ to
@code{jbuck@@synopsys.com}. Please do @emph{not} use me as a resource
@ -62,85 +63,88 @@ You can find this FAQ at
or in HTML form at @file{http://www.cerfnet.com/~mpcline/On-Line-C++-FAQs/}.
@menu
* basics:: What is g++? How do I get it?
* egcs and 2.8.0:: The next generation(s) of g++
* installation:: How to install, installation problems
* evolution:: The Evolution of g++
* User Problems:: Commonly reported problems and bugs
* legalities:: Lawyer stuff, GPL, LGPL, etc.
* index:: Index of terms
* basics:: What is g++? How do I get it?
* egcs and 2.8.0:: The next generation(s) of g++
* installation:: How to install, installation problems
* evolution:: The Evolution of g++
* User Problems:: Commonly reported problems and bugs
* legalities:: Lawyer stuff, GPL, LGPL, etc.
* index:: Index of terms
--- The Detailed Node Listing ---
The basics: what is g++?
* latest versions::
* g++ for Unix::
* g++ for HP::
* g++ for Solaris 2.x::
* g++ for other platforms::
* 1.x vs 2.x versions::
* latest versions::
* g++ for Unix::
* g++ for HP::
* g++ for Solaris 2.x::
* g++ for other platforms::
* 1.x vs 2.x versions::
The Next Generation(s) of g++
* egcs-intro:: What is egcs?
* egcs-whats-new:: What's new in egcs vs 2.7.2?
* egcs-run-both:: How can I run both egcs and an FSF release?
* egcs-vs-2.8.0:: How will egcs affect 2.8.0?
* egcs-robustness:: How robust is egcs-1.0?
* new-in-2.8.0:: What's new in gcc 2.8.0?
* egcs-intro:: What is egcs?
* egcs-whats-new:: What's new in egcs vs 2.7.2?
* egcs-bug-fixes:: What was fixed in egcs-1.0.1?
* egcs-linux:: If I install on Linux, will it overwrite my libraries?
* egcs-run-both:: How can I run both egcs and an FSF release?
* egcs-vs-2.8.0:: How will egcs affect 2.8.0?
* egcs-robustness:: How robust is egcs?
Installation Issues and Problems
* gcc-2 + g++-1::
* what else do I need?::
* use GNU linker?::
* Use GNU assembler?::
* shared libraries::
* repository::
* repo bugs::
* Use GNU C library?::
* gcc-2 + g++-1::
* what else do I need?::
* use GNU linker?::
* Use GNU assembler?::
* shared libraries::
* repository::
* repo bugs::
* Use GNU C library?::
* Global constructor problems::
* Strange assembler errors::
* Strange assembler errors::
* Other problems building libg++::
* More size_t problems::
* Rebuild libg++?::
* co-existing versions::
* Installing on Linux::
* Linux Slackware 3.0::
* More size_t problems::
* Rebuild libg++?::
* co-existing versions::
* Installing on Linux::
* Linux Slackware 3.0::
The Evolution of g++
* version 2.7.x:: What's changed in 2.7.x from earlier versions
* libstdc++::
* version 2.7.x:: What's changed in 2.7.x from earlier versions
* libstdc++::
User Problems
* missing virtual table::
* for scope::
* const constructor::
* unused parameter warnings::
* missing virtual table::
* for scope::
* const constructor::
* unused parameter warnings::
* jump crosses initialization::
* Demangler::
* static data members::
* internal compiler error::
* bug reports::
* porting to g++::
* name mangling::
* Demangler::
* static data members::
* internal compiler error::
* bug reports::
* porting to g++::
* name mangling::
* problems linking with other libraries::
* documentation::
* templates::
* undefined templates::
* redundant templates::
* Standard Template Library::
* STL and string::
* exceptions::
* namespaces::
* agreement with standards::
* documentation::
* templates::
* undefined templates::
* redundant templates::
* Standard Template Library::
* STL and string::
* exceptions::
* namespaces::
* agreement with standards::
* compiling standard libraries::
* debugging on SVR4 systems::
* debugging on SVR4 systems::
* debugging problems on Solaris::
* X11 conflicts with libg++::
* assignment to streams::
* X11 conflicts with libg++::
* assignment to streams::
@end menu
@node basics, egcs and 2.8.0, Top, Top
@ -161,12 +165,12 @@ it is not public domain, but is protected by the GNU Public License,
or GPL (@pxref{legalities}).
@menu
* latest versions::
* g++ for Unix::
* g++ for HP::
* g++ for Solaris 2.x::
* g++ for other platforms::
* 1.x vs 2.x versions::
* latest versions::
* g++ for Unix::
* g++ for HP::
* g++ for Solaris 2.x::
* g++ for other platforms::
* 1.x vs 2.x versions::
@end menu
@node latest versions, g++ for Unix, basics, basics
@ -175,20 +179,23 @@ or GPL (@pxref{legalities}).
@cindex egcs release
The egcs project (on the Web: @file{http://www.cygnus.com/egcs/}) has
now released egcs-1.0 as of December 3, 1997.
released a bug-fix version, egcs-1.0.1, on January 6, 1998. Folks
using egcs-1.0 should upgrade, as it has some important bug fixes.
@cindex gcc/g++, version date
The current version of gcc/g++ is 2.7.2.3, released August 20, 1997.
Although that looks very recent, the only change is a minor patch to
resolve a problem with Linux and the GNU C library; users not interested
in that functionality have no reason to upgrade.
The current version of gcc/g++ is 2.8.0 (!), released January 14, 1998.
It is a huge improvement over the 2.7.x releases, and thanks to
extensive testing in the egcs framework, is perhaps the least buggy .0
gcc release anyone can remember (though there are definitely a few).
The current version of libg++ is 2.7.2, released July 4, 1996.
The last release of gcc/g++ with improvements to the C++ front end was
2.7.2, released Nov. 25, 1995, nearly two years ago.
The current version of libg++ is 2.8.0, released January 19, 1998.
However, libg++ is being deprecated; libstdc++-2.8.0 contains just the
standard C++ classes and is a subset of libg++ 2.8.0. The libstdc++
library is identical to the one included in egcs-1.0.1.
I would strongly recommend that anyone using a g++ version earlier
than 2.7.2 should upgrade if at all possible (@pxref{version 2.7.x}).
Folks who need modern C++ features should upgrade to 2.8.0 or egcs.
For some non-Unix platforms, the latest port of gcc may be an earlier
version (2.6.3, say). You'll need to use a version of libg++ that
@ -411,7 +418,7 @@ places
Eberhard Mattes did the EMX port. His address is
mattes@@azu.informatik.uni-stuttgart.de.
Read the FAQ file included with the distribution before harassing the author.
Read the FAQ file included with the distribution before harrassing the author.
@cindex Apple support
@cindex Macintosh support
@ -432,7 +439,7 @@ him directly (shebs@@cygnus.com) for more information.
@node 1.x vs 2.x versions, , g++ for other platforms, basics
@section But I can only find g++-1.42!
``I keep hearing people talking about g++ 2.7.2 (or some other number
``I keep hearing people talking about g++ 2.8.0 (or some other number
starting with 2), but the latest version I can find is g++ 1.42.
Where is it?''
@ -450,14 +457,39 @@ convention. It means ``the C++ compiler included with gcc-2.x.y.''
@chapter The Next Generation(s) of g++
@menu
* egcs-intro:: What is egcs?
* egcs-whats-new:: What's new in egcs vs 2.7.2?
* egcs-run-both:: How can I run both egcs and an FSF release?
* egcs-vs-2.8.0:: How will egcs affect 2.8.0?
* egcs-robustness:: How robust is egcs-1.0?
* new-in-2.8.0:: What's new in gcc 2.8.0?
* egcs-intro:: What is egcs?
* egcs-whats-new:: What's new in egcs vs 2.7.2?
* egcs-bug-fixes:: What was fixed in egcs-1.0.1?
* egcs-linux:: If I install on Linux, will it overwrite my libraries?
* egcs-run-both:: How can I run both egcs and an FSF release?
* egcs-vs-2.8.0:: How will egcs affect 2.8.0?
* egcs-robustness:: How robust is egcs?
@end menu
@node egcs-intro, egcs-whats-new, egcs and 2.8.0, egcs and 2.8.0
@node new-in-2.8.0, egcs-intro, egcs and 2.8.0, egcs and 2.8.0
@section What's new in gcc/g++ 2.8.0?
After a two-year wait, gcc 2.8.0 was released in January 1998, along
with libstdc++-2.8.0 and libg++-2.8.0. Note that the latter (libg++)
contains the former (libstdc++) so there is no reason to install both
library packages, but libstdc++ is required.
For those familiar with egcs, the most obvious difference between
gcc-2.8.0 and egcs-1.0 or 1.0.1 is the packaging: egcs is bundled with
libstdc++, and gcc-2.8.0 does not contain the class library. Otherwise,
except for the lack of the @code{-frepo} option and some bug fixes
that have not yet made it into gcc-2.8.0, C++ users will find the
two compilers to be almost the same at this stage, other than that 2.8.0
users may get more bogus warnings with -Wall and optimization because
some fixes to flow analysis in the presence of exceptions that egcs made
are not yet present in gcc 2.8.0.
Because the new feature lists for egcs and gcc 2.8 are almost the same,
please see @xref{egcs-whats-new} for a list of new features. It is a
fairly long list.
@node egcs-intro, egcs-whats-new, new-in-2.8.0, egcs and 2.8.0
@section What is egcs?
egcs is the Experimental GNU compiler system (see
@ -466,35 +498,39 @@ accelerate development of new gcc features by providing a more open
development model than gcc has traditionally used.
The first egcs release, egcs-1.0, came out on December 3, 1997.
The current release is egcs-1.0.1, released January 6, 1998.
Questions not addressed here may be answered in the egcs FAQ
(@file{http://www.cygnus.com/egcs/faq.html}).
@node egcs-whats-new, egcs-run-both, egcs-intro, egcs and 2.8.0
@node egcs-whats-new, egcs-bug-fixes, egcs-intro, egcs and 2.8.0
@section What new C++ features are in egcs?
@strong{Note}: unless indicated otherwise, these features are expected
to be present in g++ 2.8.0 when released.
@strong{Note}: unless indicated otherwise, these features are also
present in g++ 2.8.0.
@itemize @bullet
@item
@cindex integrated libstdc++
The standard C++ classes are integrated with the egcs release (this is
@emph{not} expected to be true of gcc-2.8.0). libg++ is not being
supported, though a version that will work with egcs has been
contributed (FIXME: pointer?). The compiler and library are configured
and built in one step.
The standard C++ classes are integrated with the egcs release (but
@strong{not} for gcc-2.8.0, which does not include the class libraries).
libg++ is not being
supported, though an add-on version that will work with egcs can be found at
@file{ftp://ftp.yggdrasil.com/private/hjl/libg++-2.8.0b6.6.tar.gz},
thanks to H.J. Lu. The compiler and library are configured and built
in one step.
@item
@cindex new template implementation
A completely new template implementation, much closer to the draft
standard. Limitations in 2.7.2.x concerning inlining template functions
will be eliminated. Static template data members, template class member
functions, partial specification, and default template arguments will be
are eliminated. Static template data members, template class member
functions, partial specification, and default template arguments are
supported. An instantiation method resembling that used in Borland C++
(instantiating functions possibly in multiple .o files and using weak
symbols to link correctly) is provided, in addition to other
options. The SGI version of STL is shipped verbatim with libstdc++.
options. The SGI version of STL is shipped verbatim with libstdc++
(libstdc++ is included with egcs, separate with gcc-2.8.0).
@item
@cindex redundant template elimination
@ -506,9 +542,9 @@ at link time.
@item
@cindex repository
@cindex -frepo
The @code{-frepo} flag is supported in egcs (it will not be in 2.8.0).
The @code{-frepo} flag is supported in egcs (it is not in 2.8.0).
However, because of the previous item, I don't recommend its use on ELF
systems.
systems, as the default method is better.
@item
@cindex new exception implementation
@ -536,7 +572,54 @@ There are many more changes: see @file{http://www.cygnus.com/egcs/c++features.ht
Features that are still missing include namespaces and templates as
template arguments.
@node egcs-run-both, egcs-vs-2.8.0, egcs-whats-new, egcs and 2.8.0
@node egcs-bug-fixes, egcs-linux, egcs-whats-new, egcs and 2.8.0
@section What was fixed in egcs-1.0.1?
@itemize @bullet
@item
Add support for Red Hat 5.0 Linux and better support for Linux
systems using glibc2.
@item
Compatibility with both egcs-1.0 and gcc-2.8 libgcc exception handling
interfaces (see below).
@item
Various bugfixes in the x86, hppa, mips, and rs6000/ppc backends.
@item
A few machine independent bugfixes, mostly to fix code generation bugs
when building Linux kernels or glibc.
@item
Fix a few critical exception handling and template bugs in the C++
compiler.
@item
Fix build problems on x86-solaris systems.
@end itemize
To avoid future compatibility problems, we strongly urge anyone who is
planning on distributing shared libraries that contain C++ code to
upgrade to egcs-1.0.1 first. See
@file{http://www.cygnus.com/egcs/egcs-1.0.1.html} for details about the
compatibility issues as well as additional information about the
bugfixes since the egcs-1.0 release.
@node egcs-linux, egcs-run-both, egcs-bug-fixes, egcs and 2.8.0
@section If I install egcs on Linux, will it overwrite my libraries?
No. If you build from sources, by default, egcs installs executables in
@code{/usr/local/bin} and libraries in @code{/usr/local/lib}, and you
can change this default if desired (see next section).
If, however, you install a package (e.g. Debian or Red Hat) that wants
to put egcs in @code{/usr/bin} and @code{/usr/lib}, then yes, you are
replacing your system compiler and C++ library (I don't know if anyone
has provided such packages yet -- proceed with caution).
@node egcs-run-both, egcs-vs-2.8.0, egcs-linux, egcs and 2.8.0
@section How can I run both egcs and an FSF release of g++ on the same machine?
The recommended approach is to provide a different argument to the
@ -553,56 +636,45 @@ ln -s /usr/local/egcs/bin/g++ /usr/local/bin/eg++
@node egcs-vs-2.8.0, egcs-robustness, egcs-run-both, egcs and 2.8.0
@section What about 2.8.0? How does egcs affect the 2.8.x development?
2.8.0 is expected Real Soon Now (I would guess by the end of 1997, but that
is only a guess). The C++ front end should be essentially the same.
2.8.0 has now been released, with essentially the same C++ front end as
egcs.
Bug fixes generated in egcs will be passed to the 2.8.x releases for
inclusion; the reverse is also taking place, though a bug fix may
appear in one before it does in the other.
appear in one before it does in the other. egcs development is expected
to proceed more quickly.
@node egcs-robustness, , egcs-vs-2.8.0, egcs and 2.8.0
@section How solid is egcs-1.0?
@section How robust is egcs?
While the 'e' stands for 'experimental', egcs has been tested thoroughly
and should be of high quality. There are a few glitches which should be
fixed shortly (in a 1.0.1 release, probably in early January):
and should be of high quality. A few glitches in the initial release
were fixed in 1.0.1. egcs-1.0 users should upgrade.
@itemize @bullet
@item
Deeply nested templates sometimes lead to a very large memory requirement
if the @code{-Wreturn-type} option is on (note: this flag is implicitly
turned on by @code{-W} or @code{-Wall}. A workaround is to give the
flag @code{-Wno-return-type} if you use @code{-Wall}.
@item
On Red Hat 5.0, it may be necessary to link all C++ programs with
@code{-lpthread} to work around an undefined symbol problem.
@item
A patch is needed to fix egcs on Solaris/X86. It is in the egcs FAQ
(see above).
@end itemize
Some memory bloat problems with deeply nested templates were fixed in
1.0.1 (though it appears that there are still a few cases where
excessive memory requirements occur).
@node installation, evolution, egcs and 2.8.0, Top
@chapter Installation Issues and Problems
@menu
* gcc-2 + g++-1::
* what else do I need?::
* use GNU linker?::
* Use GNU assembler?::
* shared libraries::
* repository::
* repo bugs::
* Use GNU C library?::
* gcc-2 + g++-1::
* what else do I need?::
* use GNU linker?::
* Use GNU assembler?::
* shared libraries::
* repository::
* repo bugs::
* Use GNU C library?::
* Global constructor problems::
* Strange assembler errors::
* Strange assembler errors::
* Other problems building libg++::
* More size_t problems::
* Rebuild libg++?::
* co-existing versions::
* Installing on Linux::
* Linux Slackware 3.0::
* More size_t problems::
* Rebuild libg++?::
* co-existing versions::
* Installing on Linux::
* Linux Slackware 3.0::
@end menu
@node gcc-2 + g++-1, what else do I need?, installation, installation
@ -701,7 +773,7 @@ debug format (e.g. Suns running SunOS 4.x), the GNU linker compresses
the debug symbol table considerably. The 2.7 version adds some symbol
table compression for ELF and Solaris targets.
Users of egcs or 2.8.0 (when released) on ELF systems should definitely
Users of egcs or 2.8.0 on ELF systems should definitely
use GNU ld (2.8 or later), as it will automatically remove duplicate
instantiations of templates, virtual function tables, or ``outlined''
copies of inline functions.
@ -1102,19 +1174,20 @@ This chapter discusses the evolution of g++ and describes what can be expected
in the future.
@menu
* version 2.7.x:: What's changed in 2.7.x from earlier versions
* libstdc++::
* version 2.7.x:: What's changed in 2.7.x from earlier versions
* libstdc++::
@end menu
@node version 2.7.x, libstdc++, evolution, evolution
@section What's new in version 2.7.x of gcc/g++
The current version of gcc/g++ is 2.7.2.2, released February 10, 1997.
The only change between 2.7.2.1 and 2.7.2.2 is that support was added
for using the GNU C library, version 2, on Linux; users not interested
in that functionality have no reason to upgrade.
The previous version of gcc/g++ is 2.7.2.1, released August 14, 1996.
The current version of libg++ is 2.7.2, released July 4, 1996.
[ This section is old now, since 2.8.0/egcs is the new stuff ] The
latest 2.7.x version was 2.7.2.2, released February 10, 1997. The only
change between 2.7.2.1 and 2.7.2.2 is that support was added for using
the GNU C library, version 2, on Linux; users not interested in that
functionality have no reason to upgrade. The previous version of
gcc/g++ was 2.7.2.1, released August 14, 1996. The libg++ version that
should be used with any 2.7.x gcc/g++ is 2.7.2, released July 4, 1996.
Note that gcc 2.7.2.1 just consists of several small patches to
gcc-2.7.2. The release is mainly
@ -1265,32 +1338,32 @@ will always be available, enhancements to it should not be expected.
@chapter User Problems
@menu
* missing virtual table::
* for scope::
* const constructor::
* unused parameter warnings::
* missing virtual table::
* for scope::
* const constructor::
* unused parameter warnings::
* jump crosses initialization::
* Demangler::
* static data members::
* internal compiler error::
* bug reports::
* porting to g++::
* name mangling::
* Demangler::
* static data members::
* internal compiler error::
* bug reports::
* porting to g++::
* name mangling::
* problems linking with other libraries::
* documentation::
* templates::
* undefined templates::
* redundant templates::
* Standard Template Library::
* STL and string::
* exceptions::
* namespaces::
* agreement with standards::
* documentation::
* templates::
* undefined templates::
* redundant templates::
* Standard Template Library::
* STL and string::
* exceptions::
* namespaces::
* agreement with standards::
* compiling standard libraries::
* debugging on SVR4 systems::
* debugging on SVR4 systems::
* debugging problems on Solaris::
* X11 conflicts with libg++::
* assignment to streams::
* X11 conflicts with libg++::
* assignment to streams::
@end menu
@node missing virtual table, for scope, User Problems, User Problems
@ -1711,7 +1784,7 @@ While there is no libg++-specific document describing the STL
implementation, SGI's web site, at
@file{http://www.sgi.com/Technology/STL/}, is an excellent resource.
Note that the SGI version of STL is the one that is included with the
egcs and 2.8.0 (when it occurs) releases of g++.
egcs and 2.8.0 releases of g++/libstdc++.
@end itemize
@ -1746,10 +1819,10 @@ template ostream& operator << (ostream&, const A<int>&);
@end example
@cindex template limitations
As of version 2.6.3, there are still a few limitations in the template
As of version 2.7.2, there are still a few limitations in the template
implementation besides the above (thanks to Jason Merrill for this info):
These are still present in version 2.7.2, but a new implementation of
templates planned for version 2.8 will eliminate them.
@strong{Note}: these problems are eliminated in egcs and in gcc-2.8.0.
@enumerate 1
@item
@ -1809,7 +1882,7 @@ void g () @{
@}
@end example
A workaround that works in version 2.6.1 and later is to specify
A workaround that works in version 2.6.1 through 2.7.2.x is to specify
@example
extern template int min (int, int);
@ -1818,9 +1891,15 @@ extern template int min (int, int);
before @code{f()}; this will force it to be instantiated (though not
emitted).
@strong{Note:} this kind of ``guiding declaration'' is not standard and
isn't supported by egcs or gcc-2.8.0, as the standard says that this
declares a ``normal'' @code{min} function which has no relation to
the template function @code{min<int>(int,int)}. But then the new
compilers have no problem inlining template functions.
@item
Member function templates are always instantiated when their containing
class is. This is wrong.
class is. This is wrong (fixed in egcs/2.8).
@end enumerate
@node undefined templates, redundant templates, templates, User Problems
@ -1902,34 +1981,20 @@ This bug is fixed in 2.7.0.
@node Standard Template Library, STL and string, redundant templates, User Problems
@section Does g++ support the Standard Template Library?
@cindex STL
@cindex Standard Template Library
The Standard Template Library (STL) uses many of the extensions that the
ANSI/ISO committee has made to templates, and g++ doesn't support
some of these yet. So if you grab HP's free implementation of STL it
isn't going to work. However, starting with libg++-2.6.2 libg++ contains a
hacked version of STL, based on work by Carsten Bormann, which permits
g++ to compile at least the containers (thanks to Per Bothner for this
text).
If you want to use the Standard Template Library, do not pass go,
upgrade immediately to gcc-2.8.0 or to egcs. The new C++ front end
handles STL very well, and the high-quality implementation of STL
from SGI is included verbatim as part of the libstdc++ class library.
Actually, as of libg++ version 2.7.2 most of this works quite well, most
of the time;
I've succeeded
in making significant use of it.
Almost all of the ObjectSpace examples (a set of
over 200 simple examples of STL usage) now work.
When version 2.8.0 is out (with its complete redesign of the template
implementation) a much more complete implementation of the
STL (based on a newer free implementation from SGI) will be included.
In the meantime, a group at the Moscow Center for Sparc Technology has
If for some reason you must use 2.7.2, you can probably get by with
the hacked-up version of the old implementation from HP that is
included with libg++-2.7.2, but it is definitely inferior and has more
problems. Alternatively, g++ 2.7.2.x users might try the following:
a group at the Moscow Center for Sparc Technology has
a port of the SGI STL implementation that mostly works with gcc-2.7.2.
See
@file{http://www.ipmce.su/people/fbp/stl/stlport.html}.
In addition, there are several commercial suppliers of STL implementations;
ObjectSpace's version supports gcc-2.7.x.
Mumit Khan has produced an ``STL newbie guide'' with lots of information
on using STL with gcc. See
@ -1938,6 +2003,8 @@ on using STL with gcc. See
@node STL and string, exceptions, Standard Template Library, User Problems
@section I'm having problems mixing STL and the standard string class
[ This section is for g++ 2.7.2.x users only ]
This is due to a bug in g++ version 2.7.2 and 2.7.2.1; the compiler
is confused by the operator declarations. There is an easy workaround,
however; just make sure that the @code{<string>} header is included
@ -1981,29 +2048,34 @@ and ``VAX may also work'' (according to Mike Stump).
As of version 2.7.2, g++ recognizes the keywords @code{namespace} and
@code{using}, and there is some rudimentary code present, but almost
nothing connected with namespaces works yet. It appears that this will
still be true when 2.8.0 is released.
nothing connected with namespaces works yet.
The new versions (2.8.0/egcs) still lack namespace support, but to help
compile standard programs they make
@example
using namespace std;
@end example
a no-op.
@node agreement with standards, compiling standard libraries, namespaces, User Problems
@section What are the differences between g++ and the ARM specification of C++?
@cindex ARM [Annotated C++ Ref Manual]
@cindex exceptions
As of version 2.7.0, g++ has exception support on most but not all
platforms
(no support on MIPS-based platforms yet), but
it doesn't work right if optimization is enabled, which means the
exception
implementation is still
not really ready for production use.
Up until recently, there was no really usable exception support. If you
need exceptions, you want gcc-2.8.0 or egcs. The implementation works
fairly well. The 2.7.x version was strictly alpha quality and quite
fragile.
@cindex mutable
Some features that the ANSI/ISO standardization committee has voted in
that don't appear in the ARM are supported, notably the @code{mutable}
keyword, in version 2.5.x. 2.6.x adds support for the built-in boolean
type @code{bool}, with constants @code{true} and @code{false}. The
beginnings of run-time type identification are present, so there are
keyword, in version 2.5.x. 2.6.x added support for the built-in boolean
type @code{bool}, with constants @code{true} and @code{false}. Run-time
type identification was rudimentary in 2.7.x but is fully supported in
2.8.0, so there are
more reserved words: @code{typeid}, @code{static_cast},
@code{reinterpret_cast}, @code{const_cast}, and @code{dynamic_cast}.
@ -2011,6 +2083,7 @@ more reserved words: @code{typeid}, @code{static_cast},
As with any beta-test compiler, there are bugs. You can help improve
the compiler by submitting detailed bug reports.
[ This paragraph obsoleted by 2.8.0/egcs: ]
One of the weakest areas of g++ other than templates is the resolution
of overloaded functions and operators in complex cases. The usual
symptom is that in a case where the ARM says that it is ambiguous which
@ -2069,7 +2142,8 @@ debugging information in a format known as `DWARF'.
Although the GNU C compiler already knows how to write out symbolic debugging
information in the DWARF format, the GNU C++ compiler does not yet have this
feature yet. However, work is in progress for DWARF 2 debug support for
gcc and g++ and will be available in a future release (probably 2.8.0).
gcc and g++ and it works fairly well in 2.8.0 and egcs, though we'll
have to wait for gdb 4.17 to be released to take full advantage.
@cindex stabs
@cindex --with-stabs
@ -2235,6 +2309,10 @@ all the standard classes are in @file{-lstdc++}; you can do the link
step with @code{c++} instead of @code{g++} to search only the
@file{-lstdc++} library and avoid the LGPL'ed code in @file{-lg++}.
Note that in egcs and in gcc-2.8.0, if you do not
specify any libraries the @code{g++} command will only link in
@file{-lstdc++}, so your executable will not be affected by the LGPL.
If you wish to discuss legal issues connected with GNU software on the
net, please use @file{gnu.misc.discuss}, not the technical newsgroups.

452
gcc/cp/parse.c
View file

File diff suppressed because it is too large Load diff

8
gcc/cp/parse.y
View file

@ -3309,8 +3309,12 @@ typename_sub2:
TYPENAME SCOPE
{
if (TREE_CODE ($1) != IDENTIFIER_NODE)
$$ = lastiddecl;
got_scope = $$ = complete_type (TREE_TYPE ($$));
$1 = lastiddecl;
got_scope = $$ = complete_type (TREE_TYPE ($1));
if ($$ == error_mark_node)
cp_error ("`%T' is not a class or namespace", $1);
}
| SELFNAME SCOPE
{

23
gcc/cp/pt.c
View file

@ -866,6 +866,9 @@ check_explicit_specialization (declarator, decl, template_count, flags)
SET_DECL_EXPLICIT_INSTANTIATION (decl);
return decl;
}
else if (DECL_STATIC_FUNCTION_P (tmpl)
&& DECL_NONSTATIC_MEMBER_FUNCTION_P (decl))
revert_static_member_fn (&decl, 0, 0);
/* Mangle the function name appropriately. Note that we do
not mangle specializations of non-template member
@ -1822,11 +1825,23 @@ coerce_template_parms (parms, arglist, in_decl,
continue;
}
/* In case we are checking arguments inside a template template
parameter, ARG that does not come from default argument is
also a TREE_LIST node */
if (TREE_CODE (arg) == TREE_LIST && ! is_overloaded_fn (arg))
if (TREE_CODE (arg) == TREE_LIST
&& TREE_TYPE (arg) != NULL_TREE
&& TREE_CODE (TREE_TYPE (arg)) == OFFSET_TYPE)
{
/* The template argument was the name of some
member function. That's usually
illegal, but static members are OK. In any
case, grab the underlying fields/functions
and issue an error later if required. */
arg = TREE_VALUE (arg);
TREE_TYPE (arg) = unknown_type_node;
}
else if (TREE_CODE (arg) == TREE_LIST && ! is_overloaded_fn (arg))
{
/* In case we are checking arguments inside a template template
parameter, ARG that does not come from default argument is
also a TREE_LIST node */
is_tmpl_parm = 1;
arg = TREE_VALUE (arg);
}

4
gcc/cp/search.c
View file

@ -3220,6 +3220,10 @@ note_debug_info_needed (type)
if (current_template_parms)
return;
if (TYPE_BEING_DEFINED (type))
/* We can't go looking for the base types and fields just yet. */
return;
/* We can't do the TYPE_DECL_SUPPRESS_DEBUG thing with DWARF, which
does not support name references between translation units. Well, we

5
gcc/cp/typeck.c
View file

@ -136,6 +136,11 @@ tree
complete_type (type)
tree type;
{
if (type == NULL_TREE)
/* Rather than crash, we return something sure to cause an error
at some point. */
return error_mark_node;
if (type == error_mark_node || TYPE_SIZE (type) != NULL_TREE)
;
else if (TREE_CODE (type) == ARRAY_TYPE && TYPE_DOMAIN (type))