From: "J. Johnston" <jjohnstn@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: frame id enhancement
Date: Fri, 17 Oct 2003 19:34:00 -0000 [thread overview]
Message-ID: <3F904454.4030006@redhat.com> (raw)
In-Reply-To: <1031017181116.ZM32546@localhost.localdomain>
Kevin Buettner wrote:
> On Oct 16, 5:49pm, J. Johnston wrote:
>
>
>>It "is" a register stack on the ia64. Registers r32 - r127 for any frame all
>>come from this area. It gets bumped up by a special alloc() instruction. I'm
>>not sure I would call it unordered. It may be better to say that it is treated
>>as unordered. That would make the comments below much simpler - i.e. the
>>special_addr field is treated as unordered so it is never used to determine
>>order when comparing frames.
>
>
> For IA-64, the backing store most certainly is ordered. It is quite
> possible to have a bunch of consecutive frames which all have the same
> "sp" value. For these frames, older frames will have smaller bsp values
> than newer frames. (I.e, the backing store stack grows from lower
> addresses toward higher addresses.)
>
Just to clarify, I was referring to two different "it"s above. What I meant to
say was "I wouldn't call the special field unordered". Sorry for the confusion.
The special field may or may not be an ordered value, but generically, it
should be treated as unordered which is why I made the clarification in the comment.
-- Jeff J.
prev parent reply other threads:[~2003-10-17 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 21:15 J. Johnston
2003-10-14 21:59 ` J. Johnston
2003-10-15 21:09 ` Andrew Cagney
2003-10-15 23:12 ` J. Johnston
2003-10-16 16:09 ` Andrew Cagney
2003-10-16 19:06 ` J. Johnston
2003-10-16 21:06 ` Andrew Cagney
2003-10-16 21:49 ` J. Johnston
2003-10-16 23:32 ` J. Johnston
2003-10-17 13:30 ` Andrew Cagney
2003-10-17 16:32 ` J. Johnston
2003-10-17 18:11 ` Kevin Buettner
2003-10-17 19:34 ` J. Johnston [this message]
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=3F904454.4030006@redhat.com \
--to=jjohnstn@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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