From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: drow@false.org
Cc: gdb-patches@sourceware.org, orjan.friberg@axis.com,
hans-peter.nilsson@axis.com, ricard.wanderlof@axis.com
Subject: Re: [rfc] Delay slots on cris
Date: Mon, 30 Jun 2008 14:00:00 -0000 [thread overview]
Message-ID: <200806300838.m5U8ciPp005155@ignucius.se.axis.com> (raw)
In-Reply-To: <20080629024031.GA26670@caradoc.them.org> (message from Daniel Jacobowitz on Sat, 28 Jun 2008 22:40:31 -0400)
> Date: Sat, 28 Jun 2008 22:40:31 -0400
> From: Daniel Jacobowitz <drow@false.org>
> I've been auditing all uses of the frame unwind methods and this one
> seems wrong. If I understand correctly, ERP/NRP have the low bit set
> when the program was interrupted in the midst of a delay slot.
Right.
> While
> ERP is rarely saved - so by default frame_unwind_register and
> get_frame_register will find the same value - I believe the copy we
> want is the current frame's (i.e. the one whose current PC is pointing
> at the branch). Right?
That certainly sounds reasonable, but I think better Orjan chime
in here.
> [The cris target has no listed maintainers and has had no
> non-mechanical changes in just over three years. Knowing the likely
> culprits, CC'd, I assume that means it works fine :-)]
So I've heard; I haven't tested it myself.
I'm listed under "Authorized Committers" as
CRIS Hans-Peter Nilsson hp@axis.com
(I just fixed the email address address).
Apparently someone pruned me from the target-maintainer section,
but that's fine. I guess we can and should find someone to put
there; I'll look into it.
brgds, H-P
next prev parent reply other threads:[~2008-06-30 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 5:37 Daniel Jacobowitz
2008-06-30 14:00 ` Hans-Peter Nilsson [this message]
2008-06-30 14:01 ` Orjan Friberg
2008-06-30 14:25 ` drow
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=200806300838.m5U8ciPp005155@ignucius.se.axis.com \
--to=hans-peter.nilsson@axis.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=orjan.friberg@axis.com \
--cc=ricard.wanderlof@axis.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