m2-internship/libunwind-eh_elf
1
0
Fork 0
mirror of https://github.com/tobast/libunwind-eh_elf.git synced 2024-06-30 21:21:45 +02:00
Code Issues Releases Activity

Update to reflect currently reality.

Browse source 
(Logical change 1.275)
This commit is contained in:
hp.com!davidm 2004-10-15 13:37:27 +00:00
parent 07e4c82af8
commit 75b6719352
1 changed files with 21 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
README
View file

@ -8,13 +8,12 @@ information yet, so its utility is limited. Similarly, the HP-UX/IPF
support is incomplete, though it is sufficient to do a basic support is incomplete, though it is sufficient to do a basic
backtrace. unw_resume() is not supported, however. backtrace. unw_resume() is not supported, however.
* Important GCC v3.4.0 Caveat * Important GCC v3.4.[012] Caveat
GCC v3.4.0 breaks C++ ABI compatibility and because of that, libunwind GCC v3.4.[012] break C++ ABI compatibility and because of that,
cannot easily be used as the unwinder for GCC v3.4.0. The GCC libunwind cannot easily be used as the unwinder. The GCC developers
developers are aware of the problem [1] and the expectation is that are aware of the problem [1] and the the problem has been fixed for
the problem will be fixed with GCC v3.4.1. In the meantime, it may be GCC v3.4.3.
best to avoid using GCC v3.4.0.
[1] http://gcc.gnu.org/ml/gcc/2004-04/msg00989.html [1] http://gcc.gnu.org/ml/gcc/2004-04/msg00989.html
@ -35,7 +34,16 @@ testing, you may want to use a prefix of /usr/local instead.
* Building with Intel compiler * Building with Intel compiler
** Up to version 7 ** Version 8 and later
Starting with version 8, the preferred name for the IA-64 Intel
compiler is "icc" (same name as on x86). Thus, the configure-line
should look like this:
$ ./configure CC=icc CFLAGS="-g -O3 -ip" CXX=icc CCAS=gcc CCASFLAGS=-g \
LDFLAGS="-L$PWD/src/.libs"
** Version 7
To build libunwind with the Intel Electron compiler (ECC), it is To build libunwind with the Intel Electron compiler (ECC), it is
recommended to run configure like this: recommended to run configure like this:
@ -52,15 +60,6 @@ called "__dummy" in the declaration of "struct ia64_fpreg". Without
that member, variables of type unw_context_t won't be aligned that member, variables of type unw_context_t won't be aligned
properly. properly.
** Version 8 and later
Starting with version 8, the preferred name for the IA-64 Intel
compiler is "icc" (same name as on x86). Thus, the configure-line
should look like this:
$ ./configure CC=icc CFLAGS="-g -O3 -ip" CXX=icc CCAS=gcc CCASFLAGS=-g \
LDFLAGS="-L$PWD/src/.libs"
* Building on HP-UX * Building on HP-UX
For the time being, libunwind must be built with GCC on HP-UX. For the time being, libunwind must be built with GCC on HP-UX.
@ -105,6 +104,12 @@ or C libraries, it just means that for certain corner cases, unwinding
will fail. Since they're corner cases, it is not likely for will fail. Since they're corner cases, it is not likely for
applications to trigger them. applications to trigger them.
Note: If you get lots of errors in Gia64-test-nat and Lia64-test-nat, it's
almost certainly a sign of an old assembler. The GNU assembler used
to encode previous-stack-pointer-relative offsets incorrectly.
This bug was fixed on 21-Sep-2004 so any later assembler will be
fine.
** Expected results on x86 Linux ** Expected results on x86 Linux
The following tests are expected to fail on x86 Linux: The following tests are expected to fail on x86 Linux: