X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp-workers AT delorie DOT com
Date: Sat, 30 Apr 2011 22:41:57 +0300
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: DJGPP port of GCC: current situation and future
In-reply-to: <201104301926.p3UJQDX5002560@envy.delorie.com>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-id: <837hab5xx6.fsf@gnu.org>
References: <4DBBEE1B DOT 7090803 AT iki DOT fi> <201104301926 DOT p3UJQDX5002560 AT envy DOT delorie DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Sat, 30 Apr 2011 15:26:13 -0400
> From: DJ Delorie <dj AT delorie DOT com>
> 
> 
> > .text: reloc overflow: 0x16ce2 > 0xffff
> 
> There's a trick for this that most COFF systems switched to, to
> increase the relocation limit.  IIRC a count of 0xffff means "use
> other count" which is 32 bits.

What would it take for DJGPP to use the same trick?

> Sigh, since I'm a gcc engineer and the gcc djgpp maintainer, I suppose
> it falls on me to deal with this, yes?

If you could, it would be wonderful.  TIA.