From: sof AT dcs DOT gla DOT ac DOT uk (Sigbjorn Finne)
Subject: i386pe.x: etext and end?
28 Sep 1998 20:54:04 -0700
Message-ID: <13839.16480.757084.83000.cygnus.gnu-win32@hawaii>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: gnu-win32 AT cygnus DOT com


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 AT cygnus DOT com" with one line of text: "help".