Date: Sat, 30 Sep 2000 14:27:51 +0200 From: "Eli Zaretskii" Sender: halo1 AT inter DOT net DOT il To: Martin Str|mberg Message-Id: <2427-Sat30Sep2000142751+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5h CC: djgpp-workers AT delorie DOT com In-reply-to: <200009292235.SAA07688@delorie.com> (cvs@delorie.com) Subject: Re: djgpp: djgpp/src/libc/crt0/mcount.c References: <200009292235 DOT SAA07688 AT delorie DOT com> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Fri, 29 Sep 2000 18:35:04 -0400 > From: "cvs-ams AT delorie DOT com" > > *** djgpp/src/libc/crt0/mcount.c 1997/11/02 15:18:44 1.3 > --- djgpp/src/libc/crt0/mcount.c 2000/09/29 22:35:00 1.4 > *************** static int histlen; > *** 40,44 **** > static MTAB *mtab=0; > > ! extern int etext; > > /* called by functions. Use the pointer it provides to cache > --- 40,44 ---- > static MTAB *mtab=0; > > ! extern int etext __asm__("etext"); I might be missing something, but won't this cause the same pollution you wanted to avoid? What if the application defines `etext' somewhere in its sources?