Chapter 11. Known Causes of Trouble with GCC
This section describes known problems that affect users of GCC. Most
of these are not GCC bugs per se--if they were, we would fix them.
But the result for a user may be like the result of a bug.
Some of these problems are due to bugs in other software, some are
missing features that are too much work to add, and some are places
where people's opinions differ as to what is best.
11.1. Actual Bugs We Haven't Fixed Yet
The fixincludes script interacts badly with automounters; if the
directory of system header files is automounted, it tends to be
unmounted while fixincludes is running. This would seem to be a
bug in the automounter. We don't know any good way to work around it.
The fixproto script will sometimes add prototypes for the
sigsetjmp and siglongjmp functions that reference the
jmp_buf type before that type is defined. To work around this,
edit the offending file and place the typedef in front of the
prototypes.
When -pedantic-errors is specified, GCC will incorrectly give
an error message when a function name is specified in an expression
involving the comma operator.
