www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/12/21/04:01:08

Date: Thu, 21 Dec 2000 10:53:50 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Florian X <dos DOT fire AT aon DOT at>
cc: djgpp AT delorie DOT com
Subject: Re: DLX for C++
In-Reply-To: <3a40e8cf$0$15738@SSP1NO25.highway.telekom.at>
Message-ID: <Pine.SUN.3.91.1001221105332.28580F-100000@is>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Wed, 20 Dec 2000, Florian X wrote:

> I post the new dlx.ld:
> ==================
> OUTPUT_FORMAT("coff-go32")
> FORCE_COMMON_ALLOCATION
> SECTIONS {
>   .text : {
>     *(.text)
>     dlx_first_ctor = . ;
>     *(.ctor)
>     dlx_last_ctor = . ;
>     dlx_first_dtor = . ;
>     *(.dtor)
>     dlx_last_dtor = . ;
>     *(.gcc_exc*)
>     ___EH_FRAME_BEGIN__ = . ;
>     *(.eh_fram*)
>     ___EH_FRAME_END__ = . ;
>     *(.data)
>     *(.bss)
>     *(COMMON)
>   }
> }

Hmm, isn't it better to take djgpp.djl and simply add the dlx-specific
sections to it, or replace djgpp_*_ctor etc. with dlx_*_ctor?  I admit
I don't understand well enough what do the DLX section do here, but
the current djgpp.djl has much more entries than the above shows, so
it's possible that some features are broken if, say, .gnu.linkonce
entries aren't here.

Anyone?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019