[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Help to fix FTBS on IA64 - save the frame pointer



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello fellow IA64 porters,

please CC me, I'm not subscribed to debian-ia64. I'd like to ask you for
assistance for a porting issue I discovered. The last upload of my
package "trafficserver" failed to build from source on IA64. The build
log can be found on [1]. This is a snippet of the corresponding code [2][3]:

struct sigcontext *scxt;
#if defined(__i386__)
  asm volatile ("movl %%ebp,%0":"=r" (fp));
#elif defined(__x86_64__)
  asm volatile ("mov %%rbp,%0":"=r" (fp));
#elif defined(__arm__)
  asm volatile ("mov %%r9,%0":"=r" (fp));
#endif
...
// more architecture dependent stuff later

The problem is obviously that gcc 4.6 enabled
- -Werror=unused-but-set-variable (whereas gcc 4.4 before probably
didn't), which caused the FTBS on IA64 now. The preprocessor directives
produce no architecture-dependent code for IA64, which makes the
variable indeed to be unused on IA64.

That's not the actual problem, of course. The problem is, the code is a
no-op on IA64. The basic idea is to save and restore the frame pointer.
However I have no clue about IA64's ABI calling conventions and I have
no access to a IA64 machine to eventually test patches, so I'm a bit
lost here. That's why I am asking for assitance.

Previously the package built fine on IA64 after I ported some minor
problems. However the package was/is probably not functional with
respect to this piece of code, which compiled to a no-op function just
fine before.

[1]
https://buildd.debian.org/status/fetch.php?pkg=trafficserver&arch=ia64&ver=3.0.1-1&stamp=1313026983
[2]
http://svn.apache.org/viewvc/trafficserver/traffic/trunk/lib/ts/ink_stack_trace.cc?view=markup
[3]
https://alioth.debian.org/scm/viewvc.php/ext-maint/trafficserver/trunk/lib/ts/ink_stack_trace.cc?view=markup&root=collab-maint
- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOVCuKAAoJEMcrUe6dgPNtgJQQAMAVkW7rkVYs68894w0Yjxw/
x5dGXI3cmqdYvsyR324rcUN+Tf5unPmL0RiYLtGGG/4Um9P7xt42Ls6Mw/hDfjWm
4nflMzKMrNxxvBkOI7WaI1XAGOnj+LEPtZNaz3MKN+uPtiXwL34H/z5ThAWaZxWQ
mdBz5LY5tWlLDk6miQQTrVKX2Zk9/upGz0c+dRuQeCecdxardavFKJ4R5NuHRsM0
ihWX8o7uNAbSULaAdwBT6VW//GEEx4GcODn5x4Pd+xuEOu//p5fOnp/5U0M/mQLz
m3RDTav8/lkBocwfPAU44UAwk30FFJJfVJdcnqzQgEQvRiEezvszf3hE2czS7STw
JATm5yvGv2VT3nfxS1w8DA08M8T6Edgs0DfOmADN1f7099kJ9FJEjQ5MJX+H9mAv
GTxh80oGERGWudzEhTjpfbU4dwY43IA29x11Qg67wCHK0/e/iqn+sRilgR+8+bX9
S5FZ/xxVxoQwFgwXRJjQmT4V4uTo6qa4nPEMdmQgAky068EyOMyCLCLI+VHLarg4
UFtDqKlMeR/2Ijw/PXy3ySdNckWtz1SMmFDLSbVlF2RpoNXFrAn3r9nrf8jmNIMv
mEJsQ4Qd64ZwYaIQrquJC9Bzg0gDOnNV5SOfzW3M24TqmvU/bPpTiZz20NkJ9ATm
+gMYLwoRqBgD8akFj8hx
=HuiP
-----END PGP SIGNATURE-----


Reply to: