X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp-workers AT delorie DOT com
RazorGate-KAS: Status: not_detected
RazorGate-KAS: Rate: 0
RazorGate-KAS: Envelope from: 
RazorGate-KAS: Version: 5.5.3
RazorGate-KAS: LuaCore: 80 2014-11-10_18-01-23
 260f8afb9361da3c7edfd3a8e3a4ca908191ad29
RazorGate-KAS: Lua profiles 69136 [Nov 12 2014]
RazorGate-KAS: Method: none
From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp-workers AT delorie DOT com]" <djgpp-workers AT delorie DOT com>
Subject: DJGPP port of GCC: current status
To: djgpp-workers AT delorie DOT com
Message-ID: <56AE6BDA.6050208@iki.fi>
Date: Sun, 31 Jan 2016 22:17:30 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Uploaded new files for DJGPP port of gcc-5.3.0 (this time with also Ada compiler included)

Part of changes are now committed to GCC SVN server (trunk only). Changes left out:

1) Directory and library renaming to satisfy DJGPP file name restrictions when LFN is not in use.
('X.Y.Z' -> 'X.YZ',  '++' -> 'xx', utc). I guess that there could be acceptable solution for the first:
one have configure option --program-transform-name, we could have also something similar for
using version in directory names. I do not however have acceptable solution for library renaming
(libstdc++ -> libstdcxx) which I would hope to to get into official GCC sources (my current solution
is too ugly). Anyway nothing of these things could go even in development state 3 which has now
ended

2) Some small problems with GNU fortran library, I have submitted patch for one of them, but it got
stuck. I'll have most likely to wait for creating gcc_6_branch before trying again

3) Ada changes: Freshly built gnatmake.exe did not work until recently, so nothing is submitted yet.
Actual problem with gnatmake not working in GCC build process was incorrect normalization of
path in format /dev/X/.... (drive name prefix added blindly)

We are going to have port of gcc-6.1.0 which it is going to be released unless something unexpected
happens.

Since gcc-5 cross-native build from Linux also seems to work without serious problems for all
languages (I could perform entire build of DJGPP packages of port of GCC under Linux. Doing native
bootstrap acts however as test that the compiler works well enough. Such testing is not done when
performing cross-native build

Andris