[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
gplink stack sections
From: Craig Franklin ####@####.#### Date: 17 Jul 2004 22:03:19 +0100 Message-Id: <1090098268.3284.59.camel@r2d2> Some of you may be aware that gplink can create stack sections at link time. This is accomplished using the stack directive in a linker script. STACK size=<value> A section ".stack" of size <value> is created. A symbol _stack is also created. It points to the first address (lowest value) of the stack. mplink behaves in the same way. gplink has two extensions. The first is that the stack can be specified on the command line, -t <value> or --stack <value>. This feature allows stacks to be used with modifying the provided linker scripts. The second extension is new. A _stack_end symbol is added. This symbol points to the end of the stack. This will help with downward growing stacks and could be used for detecting stack overflow. Keep in mind that using this extension will make your project incompatible with mplink. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |