This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/13466] New: Failures with ARM EABI
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 02 Dec 2011 14:06:03 +0000
- Subject: [Bug tapsets/13466] New: Failures with ARM EABI
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13466
Bug #: 13466
Summary: Failures with ARM EABI
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: mjw@redhat.com
Classification: Unclassified
On ARM kernels build with EABI we see the following failures:
Running /root/systemtap/testsuite/systemtap.context/context.exp ...
FAIL: int64 function arguments -- numeric
FAIL: int64 function arguments -- numeric --kelf --ignore-dwarf
This is because these tests pass 'long long' arguments.
It seems this differs between ARM calling conventions, newer calling
conventions mandate: "64-bit function parameters passed in registers are
aligned to an even-numbered register instead of using the next available pair."
This could be fixed by taking this into account in tapset/arm/registers.stp
u/s64_arg. But that would break other arm calling conventions.
(Also this would move some of the arguments out of registers and onto the
stack, which arm/registers.stp arch functions aren't yet prepared to handle.)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.