From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.5 unwind problem with rp <- r0
Date: Tue, 11 May 2004 07:03:55 +0000 [thread overview]
Message-ID: <16544.31451.856507.322800@napali.hpl.hp.com> (raw)
In-Reply-To: <4885.1083211711@kao2.melbourne.sgi.com>
>>>>> On Fri, 07 May 2004 18:12:49 +1000, Keith Owens <kaos@sgi.com> said:
Keith> On Wed, 5 May 2004 20:42:24 -0700, David Mosberger
Keith> <davidm@napali.hpl.hp.com> wrote:
>> I considered that approach but rejected it because it runs the
>> "FORTRAN constant" risk. That is, someone might write to a saved
>> register (e.g., via unw_set_br()) and end up inadvertently
>> redefining the 0 "constant" (unw_r0) to a non-zero value.
>> Perhaps what we could do is change unw_access_{gr,br,fr,ar,pr} to
>> reject attempts to write to the special save-address &unw_r0. I
>> think that would make it safe.
Keith> Unlikely, but if that is what it takes ....
Can you try what's in the current bk repository? It closely follows
your patch, apart from some naming and from switching the asm files to
actually use ".save rp, r0".
Thanks,
--david
next prev parent reply other threads:[~2004-05-11 7:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 4:08 2.6.5 unwind problem with rp <- r0 Keith Owens
2004-05-03 22:28 ` David Mosberger
2004-05-04 2:07 ` Keith Owens
2004-05-04 16:40 ` David Mosberger
2004-05-05 0:04 ` Keith Owens
2004-05-05 23:38 ` David Mosberger
2004-05-06 0:08 ` Keith Owens
2004-05-06 0:19 ` David Mosberger
2004-05-06 2:04 ` Keith Owens
2004-05-06 3:42 ` David Mosberger
2004-05-07 8:12 ` Keith Owens
2004-05-11 7:03 ` David Mosberger [this message]
2004-05-11 11:32 ` Keith Owens
2004-05-11 16:55 ` David Mosberger
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=16544.31451.856507.322800@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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