From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/9810] New: ia64 REG_IP() cannot be used as a lvalue
Date: Wed, 04 Feb 2009 01:08:00 -0000 [thread overview]
Message-ID: <20090203194222.9810.wcohen@redhat.com> (raw)
The ia64 REG_IP() for the ia64 takes a couple register values to synthesize a
value for the instruction pointer in runtime/regs.h:
#define REG_IP(regs) ((regs)->cr_iip +ia64_psr(regs)->ri)
However, the translator generates code like the following that uses REG_IP as an
lvalue for begin and end probes:
#ifdef STP_NEED_UNWIND_DATA
memset (& c->regs_buffer, 0, sizeof (c->regs_buffer));
REG_IP((& c->regs_buffer)) = (unsigned long)__builtin_return_address (0);
REG_SP((& c->regs_buffer)) = (unsigned long)& c;
c->regs = & c->regs_buffer;
#endif
This causes the following tests to fail on ia64:
systemtap.examples/interrupt/scf
systemtap.examples/io/io_submit
buildok/context_test.stp
The ri (restart instruction) points to which instruction in a bundle to restart
execution at. The ri field is part of the program status register (psr).
--
Summary: ia64 REG_IP() cannot be used as a lvalue
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: wcohen at redhat dot com
GCC host triplet: ia64
http://sourceware.org/bugzilla/show_bug.cgi?id=9810
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-02-03 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 1:08 wcohen at redhat dot com [this message]
2009-02-04 2:17 ` [Bug translator/9810] " fche 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=20090203194222.9810.wcohen@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).