From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15614] New: stapdyn only partially fills registers on ppc
Date: Wed, 12 Jun 2013 21:10:00 -0000 [thread overview]
Message-ID: <bug-15614-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15614
Bug ID: 15614
Summary: stapdyn only partially fills registers on ppc
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dyninst
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
Blocks: 14573
In Dyninst's EmitterPOWER::emitCall() on powerpc, they enforce a limit of 8
arguments in synthesized calls. This limits our current strategy of passing
all DWARF registers as a series of varargs. We already use one argument for
the probe index, and one for the number of arguments following, which only
leaves us space to pass 6 registers. That will be the ip and r1-r5.
To do more, we'll either have to extend Dyninst itself (which has a comment
stating that additional ppc arguments could go on the stack), or find a way to
build a full pt_regs and pass that as one pointer argument. The latter might
be possible to do manually, but even nicer would be native Dyninst support to
expose its spill area, also desired for bug 15386.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-06-12 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 21:10 jistone at redhat dot com [this message]
2020-06-05 13:47 ` [Bug dyninst/15614] " scox at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15614-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).