public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug tapsets/13466] New: Failures with ARM EABI
@ 2011-12-02 14:48 mjw at redhat dot com
  2011-12-07 15:50 ` [Bug tapsets/13466] " mjw at redhat dot com
  2017-05-08 20:29 ` fche at redhat dot com
  0 siblings, 2 replies; 3+ messages in thread
From: mjw at redhat dot com @ 2011-12-02 14:48 UTC (permalink / raw)
  To: systemtap

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.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug tapsets/13466] Failures with ARM EABI
  2011-12-02 14:48 [Bug tapsets/13466] New: Failures with ARM EABI mjw at redhat dot com
@ 2011-12-07 15:50 ` mjw at redhat dot com
  2017-05-08 20:29 ` fche at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: mjw at redhat dot com @ 2011-12-07 15:50 UTC (permalink / raw)
  To: systemtap

http://sourceware.org/bugzilla/show_bug.cgi?id=13466

--- Comment #1 from Mark Wielaard <mjw at redhat dot com> 2011-12-07 15:33:08 UTC ---
See also Bug 13481 - ARM register.stp arg() functions don't handle arguments
passed on the stack.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug tapsets/13466] Failures with ARM EABI
  2011-12-02 14:48 [Bug tapsets/13466] New: Failures with ARM EABI mjw at redhat dot com
  2011-12-07 15:50 ` [Bug tapsets/13466] " mjw at redhat dot com
@ 2017-05-08 20:29 ` fche at redhat dot com
  1 sibling, 0 replies; 3+ messages in thread
From: fche at redhat dot com @ 2017-05-08 20:29 UTC (permalink / raw)
  To: systemtap

https://sourceware.org/bugzilla/show_bug.cgi?id=13466

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |fche at redhat dot com
         Resolution|---                         |WONTFIX

--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
no reported problems on mainstream arm64

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-05-08 20:29 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-12-02 14:48 [Bug tapsets/13466] New: Failures with ARM EABI mjw at redhat dot com
2011-12-07 15:50 ` [Bug tapsets/13466] " mjw at redhat dot com
2017-05-08 20:29 ` fche at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).