diff options
author | Jose Flavio Aguilar Paulino <jflavio@br.ibm.com> | 2007-08-24 10:54:00 -0600 |
---|---|---|
committer | David Mosberger-Tang <davidm@koala.mostang.com> | 2007-08-24 10:54:00 -0600 |
commit | 3e24581adca378307322555d2b5e70439dbc9c19 (patch) | |
tree | bfa6bad9e315c8f2bc2d6f563716bc45a09b86c2 /README | |
parent | e6b9f350f78ecd9ef3b8a3e721f9435c94fc2562 (diff) | |
download | libunwind-3e24581adca378307322555d2b5e70439dbc9c19.tar.gz |
[PPC64] Add PPC64 entry to README and fix David's typo in ppc64/get_func_addr.c
Diffstat (limited to 'README')
-rw-r--r-- | README | 18 |
1 files changed, 18 insertions, 0 deletions
@@ -61,6 +61,24 @@ workaround is to issue the following commands before running GCC v3.3.2 or later have been fixed and do not require this workaround. +* Building for PowerPC64 / Linux + +For building for power64 you should use: + + $ ./configure CFLAGS="-g -O2 -m64" CXXFLAGS="-g -O2 -m64" + +If your power support altivec registers: + $ ./configure CFLAGS="-g -O2 -m64 -maltivec" CXXFLAGS="-g -O2 -m64 -maltivec" + +To check if your processor has support for vector registers (altivec): + cat /proc/cpuinfo | grep altivec +and should have something like this: + cpu : PPC970, altivec supported + +If libunwind seems to not work (backtracing failing), try to compile +it with -O0, without optimizations. There are some compiler problems +depending on the version of your gcc. + * Regression Testing |