invoke.texi (Precompiled Headers): Warn about known problems.

	* doc/invoke.texi (Precompiled Headers): Warn about known
	problems.

From-SVN: r80529

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index aafeafa41aadc8b1cda66c3d1dc8de5c2d798192..43aa975d65f9d08553a97763884667cf806f687e 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2004-04-08  Mark Mitchell  <mark@codesourcery.com>
+
+       * doc/invoke.texi (Precompiled Headers): Warn about known
+       problems.
+
 2004-04-08  Danny Smith  <dannysmith@users.sourceforge.net>
 
        PR c++/14808

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 8afebf5fcbb8e510b7d2db95eb40b5b778a3f65b..8c12a8b158a03e566a80c1bffba9e5912274fb6b 100644 (file)
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -11336,6 +11336,13 @@ build the project.  To make builds faster, GCC allows users to
 `precompile' a header file; then, if builds can use the precompiled
 header file they will be much faster.
 
+@strong{Caution:} There are a few known situations where GCC will
+crash when trying to use a precompiled header.  If you have trouble
+with a precompiled header, you should remove the precompiled header
+and compile without it.  In addition, please use GCC's on-line
+defect-tracking system to report any problems you encounter with
+precompiled headers.  @xref{Bugs}.
+
 To create a precompiled header file, simply compile it as you would any
 other file, if necessary using the @option{-x} option to make the driver
 treat it as a C or C++ header file.  You will probably want to use a