delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-workers-bounces using -f |
Date: | Sat, 30 Apr 2011 15:26:13 -0400 |
Message-Id: | <201104301926.p3UJQDX5002560@envy.delorie.com> |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <4DBBEE1B.7090803@iki.fi> (message from Andris Pavenis on Sat, 30 |
Apr 2011 14:10:19 +0300) | |
Subject: | Re: DJGPP port of GCC: current situation and future |
References: | <4DBBEE1B DOT 7090803 AT iki DOT fi> |
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 |
> .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. > As result one can guess that the time when we can have GCC latest > versions as native DJGPP compiler has come to end. The question is > what we are going to do. Sigh, since I'm a gcc engineer and the gcc djgpp maintainer, I suppose it falls on me to deal with this, yes?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |