Displaying 3 results from an estimated 3 matches for "eipptr".
2011 Jul 07
0
[LLVMdev] Improving Garbage Collection
...Struct;
/*
* The context for stack frames that is used during stack walking. We use pointers in place of
* direct values to support root set enumeration.
*/
struct PrtStackIterator
{
/* Stack pointer, eip, and frame pointer */
PrtRegister esp;
PrtRegister *ebpPtr;
PrtCodeAddress *eipPtr;
/* Callee-save registers */
PrtRegister *ediPtr;
PrtRegister *esiPtr;
PrtRegister *ebxPtr;
/* The Pillar compiler may inline several "virtual" frames into a single "physical" frame.
However, the stack iterator should maintain the illusion that no inli...
2011 Jul 07
4
[LLVMdev] Improving Garbage Collection
On 07.07.2011 08:31, Nate Fries wrote:
> On 7/6/2011 6:24 PM, Talin wrote:
>> The LLVM code generators and analysis passes have a much more
>> thorough knowledge of SSA value lifetimes than frontends do, and
>> therefore could avoid spilling and reloading of values when it wasn't
>> needed.
> Although this would indeed be nice, it is not done by similar
>
2011 Jul 07
2
[LLVMdev] Improving Garbage Collection
...that is used during stack walking. We use
pointers in place of ****
* direct values to support root set enumeration.****
*/****
struct PrtStackIterator ****
{****
/* Stack pointer, eip, and frame pointer */****
PrtRegister esp;****
PrtRegister *ebpPtr;****
PrtCodeAddress *eipPtr;****
/* Callee-save registers */****
PrtRegister *ediPtr;****
PrtRegister *esiPtr;****
PrtRegister *ebxPtr;****
/* The Pillar compiler may inline several "virtual" frames into a single
"physical" frame.****
However, the stack iterator should main...