[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hpux-devtools
Subject:    Re:  HPUX-DEVTOOLS: What should go with ALLOCA_FRAME for backtracing purposes ?
From:       Dennis Handly <dhandly () cup ! hp ! com>
Date:       2001-04-26 20:36:16
[Download RAW message or body]

Dennis Handly writes:
> Note that R3 and possibly R4 need to point to the top of the fixed part.
               ^^^
Oops, OR.
 
> depending on the size of the static part IIUC. Just for curiosity: is
> there a specific reason for this choice (that is, for the convention to
> use one register or another)?

It should be explained in the document below.  R3 would already be used
if there were a large frame.
 
> If I understand your comment correctly, the "previous sp value" should be
> read as "the value before the first such dynamic allocation".
> Is this correct?

Yes.

> > http://devresource.hp.com/devresource/Docs/DocLib_Refs.html#archrefs
> seems it explains *what* the function does, but not *how*. I suppose the
> sources are not available (aren't they?), so I was wondering if
> the "how" was explained somewhere else.

It looks at the bits, the rest is programming magic.  :-)
(Not available.)
  
> I misread a piece of the runtime document which talks about a
> millicode routine called when a dynamically sized object is allocated
 Olivier

That may only be used for Ada.
 _________________________________________________________________
 To leave this mailing list, send mail to majordomo@cxx.cup.hp.com
    with the message UNSUBSCRIBE hpux-devtools
 _________________________________________________________________

[prev in list] [next in list] [prev in thread] [next in thread]