Known Causes Of Trouble With Gcc; Actual Bugs We Haven't Fixed Yet; Cross-Compiler Problems; Interoperation - Red Hat ENTERPRISE LINUX 3 - USING GCC Using Instructions

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
is automounted, it tends to be unmounted while
a bug in the automounter. We don't know any good way to work around it.
The script will sometimes add prototypes for the
•
fixproto
tions that reference the
offending file and place the typedef in front of the prototypes.
When
•
-pedantic-errors
tion name is specified in an expression involving the comma operator.

11.2. Cross-Compiler Problems

You may run into problems with cross compilation on certain machines, for several reasons.
Cross compilation can run into trouble for certain machines because some target machines' assem-
•
blers require floating point numbers to be written as integer constants in certain contexts.
The compiler writes these integer constants by examining the floating point value as an integer and
printing that integer, because this is simple to write and independent of the details of the floating
point representation. But this does not work if the compiler is running on a different machine with
an incompatible floating point format, or even a different byte-ordering.
In addition, correct constant folding of floating point values requires representing them in the target
machine's format. (The C standard does not quite require this, but in practice it is the only way to
win.)
It is now possible to overcome these problems by defining macros such as
doing so is a substantial amount of work for each target machine. .
At present, the program
•
does not work in a cross compile environment.

11.3. Interoperation

This section lists various difficulties encountered in using GCC together with other compilers or with
the assemblers, linkers, libraries and debuggers on certain systems.
On many platforms, GCC supports a different ABI for C++ than do other compilers, so the object
•
files compiled by GCC cannot be used with object files generated by another C++ compiler.

Known Causes of Trouble with GCC

script interacts badly with automounters; if the directory of system header files
type before that type is defined. To work around this, edit the
jmp_buf
is specified, GCC will incorrectly give an error message when a func-
which adds debug support to object files on MIPS systems
mips-tfile
is running. This would seem to be
fixincludes
sigsetjmp
Chapter 11.
and func-
siglongjmp
. But
REAL_VALUE_TYPE