i386pe.x: etext and end?
Fergus Henderson
fjh@cs.mu.OZ.AU
Wed Sep 30 10:52:00 GMT 1998
On 29-Sep-1998, DJ Delorie <dj@delorie.com> wrote:
> end and etext are "special" so they don't have underscores
> to make sure they don't interfere with functions or variables
> your program may provide (ansi/posix compliance and all that).
>
> However, you can access them using gcc extensions:
>
> extern int end asm("end");
>
> void *foo()
> {
> return (void *)&end;
> }
>
> However, since they're deprecated, there is *no* sanctioned
> way of getting at them. You shouldn't be using them at all
> unless you absolutely can't avoid it.
Sure, "end" and "etext" are deprecated -- I assume this is
because it could cause name clashes on systems which don't
prefix ordinary C symbols with underscores.
But what about "__end__" and "__etext__"?
They're not deprecated, are they?
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh > | of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3 | -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
More information about the Cygwin
mailing list