From: "Jan Beulich" <JBeulich@novell.com>
To: <cary@cup.hp.com>,<wilson@specifixinc.com>
Cc: <david_mosberger@hp.com>,<binutils@sources.redhat.com>
Subject: Re: [PATCH] ia64: unwind directive handling
Date: Mon, 13 Jun 2005 07:07:00 -0000 [thread overview]
Message-ID: <s2acdc2f.071@lyle.provo.novell.com> (raw)
>>> Cary Coutant <cary@cup.hp.com> 10.06.05 23:52:01 >>>
>> I checked the SCRA. Appendix B constains tables listing all of the
>> valid
>> unwind encodings. This does not include psp_psprel. I see that it
>> comes
>> from the .vframepsp directive. Curiously, the asm language manual has
>> two
>> typos in the vframepsp docs. It emits two unwind records, and both of
>> them
>> are mispelled. Maybe this is a late change that was never properly
>> documented.
>> How do you know that P8 r=0 is correct?
>
>Jim is right -- there is no psp_psprel unwind directive, and Format P8,
>r=0 is unassigned.
As I said, ias uses this, so it can't be completely invalid.
>If you think about it, storing the previous stack pointer at a location
>relative to psp is pointless at best, since you would need to know the
>psp in order to recover the psp!
Hmm, indeed. This, however, still doesn't mean no change is needed; .vframepsp itself is pointless, then, and support for it should be removed.
Jan
next reply other threads:[~2005-06-13 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 7:07 Jan Beulich [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 10:31 Jan Beulich
2005-07-01 3:10 ` James E Wilson
2005-06-15 15:31 Jan Beulich
2005-06-10 21:52 Cary Coutant
2005-06-10 13:21 Jan Beulich
2005-05-23 10:19 Jan Beulich
2005-06-10 0:07 ` James E Wilson
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=s2acdc2f.071@lyle.provo.novell.com \
--to=jbeulich@novell.com \
--cc=binutils@sources.redhat.com \
--cc=cary@cup.hp.com \
--cc=david_mosberger@hp.com \
--cc=wilson@specifixinc.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).