This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
i386pe.x: etext and end?
- To: gnu-win32 at cygnus dot com
- Subject: i386pe.x: etext and end?
- From: Sigbjorn Finne <sof at dcs dot gla dot ac dot uk>
- Date: Mon, 28 Sep 1998 09:30:23 +0100 (BST)
Hi,
apologies if this has been discussed before on the list, but
the definition of etext and end is a little bit odd in i386pe.x.
To quote from the version supplied with binutils-980830:
...
.text __image_base__ + __section_alignment__ :
{
...
etext = .;
*(.gcc_except_table)
}
...
.endjunk BLOCK(__section_alignment__) :
{
/* end is deprecated, don't use it */
end = .;
__end__ = .;
}
Is the omission of a prefix of (at least) one underscore to these two
symbols (end and etext) intentional? (Why not use "PROVIDE(_etext
=.);" to achieve the same effect instead?)
I guess what I'm really asking is what's the sanctioned way of getting
at these two syms from within straight C here, rely on asm labels or
not?
thx,
--Sigbjorn
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".