Sender: nate AT cartsys DOT com
Message-ID: <35F2B666.90D3201@cartsys.com>
Date: Sun, 06 Sep 1998 09:20:54 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
MIME-Version: 1.0
To: Ilya Ryzhenkov <orangy AT inetlab DOT com>
CC: djgpp workers list <djgpp-workers AT delorie DOT com>
Subject: Re: Exceptions, linker and other ...
References: <35F16687 DOT 5C81F35E AT inetlab DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Ilya Ryzhenkov wrote:
> 
> Greetings !
> 
> While updating DLM manager to v2.02 I'm going mad with
> several things, can anyone help ?
> 
> 1. Exceptions. Where can I get information on how exceptions
> are handled internally ? They constantly crash my engine ...

Read the source?

Also, there is an alternate exception implementation,
`-fsjlj-exceptions', which implements them with setjmp/longjmp.  One or
the other might be easier to support.  Best would be both, of course.

> 2. Linker script. I need a linker script, which leave all the
> stuff alone while linking with `ld -r', i.e. each section
> goes to the same section, etc... Should I know all
> possible section names ? I need something like :
> SECTIONS {
>   * : { *(.*) }
> }

Not sure, do the `ld' docs not say?

> Btw, how gcc (ld?) decides when to stubify output ? By the
> output file suffix or whatever else ?

I think the `specs' file describes it, but its syntax is highly arcane.

> 
> 3. Is their any tool, which can show the reason of including
> some .o from libc.a ? I.e. the symbol used, which require other, etc..
> I should minimize my stub (it is now 56k!), so I need to eliminate
> as much code as possible using synonimous constructions in the
> time non-critical places.
> If there is none, I will make one.

Maybe it would be possible to hack into `ld'?

HTH
-- 

Nate Eldredge
nate AT cartsys DOT com