Re: patch for i386go32.c

[Ian Lance Taylor <ian@zembu.com>]

   From: "Mark E." <snowball3@bigfoot.com>
   Date: Mon, 9 Aug 1999 18:59:38 -0400

   While testing the data alignment changes, I noticed that i386go32.sc (ugh) doesn't 
   have any code to handle C++ EH like DJGPP's own linker script does.

   ld/ChangeLog:

   1999-08-09 Mark Elbrecht <snowball3@bigfoot.com>

   * scripttempl/i386go32.sc: Update to handle C++ exceptions.

   *** scripttempl/i386go32.sc.orig	Tue Aug  3 12:12:48 1999
   --- scripttempl/i386go32.sc	Mon Aug  9 18:29:44 1999
   *************** SECTIONS
   *** 33,38 ****
   --- 33,43 ----
	 djgpp_last_dtor = . ;}
	 *(.data)
	 ${RELOCATING+*(.gnu.linkonce.d*)}
   +     ${RELOCATING+*(.gcc_exc*)
   +     ___EH_FRAME_BEGIN__ = . ;
   +     *(.eh_fram*)
   +     ___EH_FRAME_END__ = . ;
   +     LONG(0)};
	 ${RELOCATING+edata  =  . ; _edata = .};
	 ${RELOCATING+. = ALIGN(${SEGMENT_SIZE});}
       }

I checked this in.

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?

Ian