From: pavenis AT lanet DOT lv
Message-ID: <B0000097729@stargate.astr.lu.lv>
To: "Mark E." <snowball3 AT bigfoot DOT com>, djgpp-workers AT delorie DOT com,
        binutils AT sourceware DOT cygnus DOT com, djgpp-workers AT delorie DOT com
Date: Tue, 10 Aug 1999 19:58:08 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: patch for i386go32.c
In-reply-to: <199908101321.NAA93518@out4.ibm.net>
References: <19990810030743 DOT 6431 DOT qmail AT daffy DOT airs DOT com>
X-mailer: Pegasus Mail for Win32 (v3.11)
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 10 Aug 99, at 9:22, Mark E. wrote:

> >    +     ${RELOCATING+*(.gcc_exc*)
> >    +     ___EH_FRAME_BEGIN__ = . ;
> >    +     *(.eh_fram*)
> >    +     ___EH_FRAME_END__ = . ;
> >    +     LONG(0)};
> > I checked this in.
> 
> Thanks once again.
> 
> > 
> > However, I'll note that none of the other targets see the need to
> > define __EH_FRAME_{BEGIN,END}__, or to add the LONG(0).  That's
> > because other targets use the gcc crtbegin/crtend support.  Why not
> > make DJGPP work like other gcc targets?
> > 
> 
> I wasn't around when it was decided how to handle g++ exceptions. I've added djgpp-
> workers in hopes that someone who was around then there has an answer.
> 

This approach were used since port of gcc-2.8.1 (Robert Hoehne) 
suggested it as far as I remeber.

Once I tried crtbegin, crtend with egcs-1.1.... (I don't remeber which 
exactly) and I had problems (at least I remember so). Maybe it's 
time to try once more.

Andris