Message-Id:	<199908152158.XAA02650@robby.dittmannsdorf.de>
From:	Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Organization:	none provided
To:	djgpp-workers AT delorie DOT com
Date:	Mon, 16 Aug 1999 00:00:28 +0200
MIME-Version:	1.0
Subject:	Re: patch for i386go32.c
CC:	"Mark E." <snowball3 AT bigfoot DOT com>, Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
References:	<199908101850 DOT SAA70660 AT out2 DOT ibm DOT net>
In-reply-to:	<Pine.SUN.3.91.990811091743.26903D-100000@is>
X-mailer:	Pegasus Mail for Win32 (v3.11)
Reply-To:	djgpp-workers AT delorie DOT com

> Robert, can you please tell what was the cause to put __EH_FRAME_*
> into the linker scripts?  I know that at one time users who had

When I made the gcc 2.8.0 port of DJGPP I had to find a soultion
to enable the exeception support in DJGPP. The exception tables
are initialized at startup via the register_frame_info function
(at least at that time). gcc 2.8.0 was out befor DJGPP 2.02 was ready.
So I had to place the symbols in the linker script and writing a
small initializing file (crtf..c) which I distributed together with the
gcc archive and a modified specs file, where the crtf.o was linked
in before crt0.o.

Now, from DJGPP 2.02 on, the symbols in the linker script are not
longer used and also not the crtf file.

BUT WARNING: I don't know the current state of the next gcc distribution,
but since the specs file is removed from the DJGPP distrib but not the file
djgpp.djl, the reference to crtf.o in the specs file distributed with gcc
have to be removed, otherwise we will get undefined references, if someone
uses the specs file from the gcc distribution together with the djgpp.djl
from the DJGPP distribution.



******************************************************
* email:   Robert Hoehne <robert DOT hoehne AT gmx DOT net>     *
* Post:    Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW:     http://www.tu-chemnitz.de/~sho/rho        *
******************************************************

- Raw text -