Message-Id: <199908101321.NAA93518@out4.ibm.net>
From: "Mark E." <snowball3 AT bigfoot DOT com>
To: binutils AT sourceware DOT cygnus DOT com, djgpp-workers AT delorie DOT com
Date: Tue, 10 Aug 1999 09:22:25 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: patch for i386go32.c
In-reply-to: <19990810030743.6431.qmail@daffy.airs.com>
References: <199908092259 DOT WAA62234 AT out4 DOT ibm DOT net> (snowball3 AT bigfoot 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

>    +     ${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.

Mark

--- 
Mark Elbrecht, snowball3 AT bigfoot DOT com
http://snowball.frogspace.net/