Related articles |
---|
Reg. Stack allocation and profiling tools in X86 gtg418c@mail.gatech.edu (Subramanian Ramaswamy) (2004-09-13) |
Re: Reg. Stack allocation and profiling tools in X86 irogers@cs.man.ac.uk (Ian Rogers) (2004-09-14) |
From: | Ian Rogers <irogers@cs.man.ac.uk> |
Newsgroups: | comp.compilers |
Date: | 14 Sep 2004 16:56:59 -0400 |
Organization: | Dept of Computer Science, University of Manchester, U.K. |
References: | 04-09-081 |
Keywords: | 386, storage |
Posted-Date: | 14 Sep 2004 16:56:59 EDT |
You can watch the memory allocated to a process in
"/proc/<process_id>/maps" on Linux. X86 stacks grow down and the heap
(top of bss - set by brk) grows up. You also have mmap, which is used to
allocate arbitrary pages of memory.
Ian
Subramanian Ramaswamy wrote:
> Hi,
>
> How is the heap and stack size allocated in X86? Do they start off at
> both ends and keep coming towards each other as they grow as in MIPS?
>
> If it is like above, is there any profiling tool that will help me
> figure out the maximum stack size for benchmarks on X86, so I can filter
> out all the stack references from the memory trace I plan to generate.
> [It varies from one operating system to another. -John]
>
Return to the
comp.compilers page.
Search the
comp.compilers archives again.