| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This section lists various difficulties encountered in using GCC together with other compilers or with the assemblers, linkers, libraries and debuggers on certain systems.
This effect is intentional, to protect you from more subtle problems. Compilers differ as to many internal details of C++ implementation, including: how class instances are laid out, how multiple inheritance is implemented, and how virtual function calls are handled. If the name encoding were made the same, your programs would link against libraries provided from other compilers--but the programs would then crash when run. Incompatible libraries are then detected at link time, rather than at run time.
Many systems come with header files that won't work with GCC unless
corrected by fixincludes. The corrected header files go in a new
directory; GCC searches this directory before `/usr/include'.
If you use `-I/usr/include', this tells GCC to search
`/usr/include' earlier on, before the corrected headers. The
result is that you get the uncorrected header files.
Instead, you should use these options (when compiling C programs):
-I/usr/local/lib/gcc-lib/target/version/include -I/usr/include |
For C++ programs, GCC also uses a special directory that defines C++ interfaces to standard C subroutines. This directory is meant to be searched before other standard include directories, so that it takes precedence. If you are compiling C++ programs and specifying include directories explicitly, use this option first, then the two options above:
-I/usr/local/lib/g++-include |
double on an 8-byte
boundary, and it expects every double to be so aligned. The Sun
compiler usually gives double values 8-byte alignment, with one
exception: function arguments of type double may not be aligned.
As a result, if a function compiled with Sun CC takes the address of an
argument of type double and passes this pointer of type
double * to a function compiled with GCC, dereferencing the
pointer may cause a fatal signal.
One way to solve this problem is to compile your entire program with GCC.
Another solution is to modify the function that is compiled with
Sun CC to copy the argument into a local variable; local variables
are always properly aligned. A third solution is to modify the function
that uses the pointer to dereference it via the following function
access_double instead of directly with `*':
inline double
access_double (double *unaligned_ptr)
{
union d2i { double d; int i[2]; };
union d2i *p = (union d2i *) unaligned_ptr;
union d2i u;
u.i[0] = p->i[0];
u.i[1] = p->i[1];
return u.d;
}
|
Storing into the pointer can be done likewise with the same union.
malloc function in the `libmalloc.a' library
may allocate memory that is only 4 byte aligned. Since GCC on the
Sparc assumes that doubles are 8 byte aligned, this may result in a
fatal signal if doubles are stored in memory allocated by the
`libmalloc.a' library.
The solution is to not use the `libmalloc.a' library. Use instead
malloc and related functions from `libc.a'; they do not have
this problem.
_dlclose, _dlsym or _dlopen
when linking, compile and link against the file
`mit/util/misc/dlsym.c' from the MIT version of X windows.
cc does not
compile GCC correctly. We do not yet know why. However, GCC
compiled on earlier HP-UX versions works properly on HP-UX 9.01 and can
compile itself properly on 9.01.
alloca or variable-size arrays. This is because GCC doesn't
generate HP-UX unwind descriptors for such functions. It may even be
impossible to generate them.
(warning) Use of GR3 when frame >= 8192 may cause conflict. |
These warnings are harmless and can be safely ignored.
IBM has produced a fixed version of the assembler. The upgraded assembler unfortunately was not included in any of the AIX 3.2 update PTF releases (3.2.2, 3.2.3, or 3.2.3e). Users of AIX 3.1 should request PTF U403044 from IBM and users of AIX 3.2 should request PTF U416277. See the file `README.RS6000' for more details on these updates.
You can test for the presence of a fixed assembler by using the command
as -u < /dev/null |
If the command exits normally, the assembler fix already is installed. If the assembler complains that `-u' is an unknown flag, you need to order the fix.
extern int foo; ... foo ... static int foo; |
will cause the linker to report an undefined symbol foo.
Although this behavior differs from most other systems, it is not a
bug because redefining an extern variable as static
is undefined in ISO C.
LANG environment variable to
`C' or `En_US'.
size_t. You should change `sys/types.h' by adding these
lines around the definition of size_t:
#ifndef _SIZE_T #define _SIZE_T actual-typedef-here #endif |
GCC uses the same convention as the Ultrix C compiler. You can use these options to produce code compatible with the Fortran compiler:
-fcall-saved-r2 -fcall-saved-r3 -fcall-saved-r4 -fcall-saved-r5 |
-L/usr/local/lib/gcc-lib/we32k-att-sysv/2.8.1 -lgcc -lc_s |
The first specifies where to find the library `libgcc.a' specified with the `-lgcc' option.
GCC does linking by invoking ld, just as cc does, and
there is no reason why it should matter which compilation program
you use to invoke ld. If someone tracks this problem down,
it can probably be fixed easily.
ecvt, fcvt and gcvt. Given valid
floating point numbers, they sometimes print `NaN'.
Or use the `-noasmopt' option when you compile GCC with itself, and then again when you compile your program. (This is a temporary kludge to turn off assembler optimization on Irix.) If this proves to be what you need, edit the assembler spec in the file `specs' so that it unconditionally passes `-O0' to the assembler, and never passes `-O2' or `-O3'.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |