invoke.texi (Precompiled Headers): Warn about known problems.
* doc/invoke.texi (Precompiled Headers): Warn about known problems. From-SVN: r80529
This commit is contained in:
parent
4a77e08cfc
commit
f7b6f250d7
2 changed files with 12 additions and 0 deletions
|
@ -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
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue