X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp-workers AT delorie DOT com
Message-ID: <52754597.9000204@iki.fi>
Date: Sat, 02 Nov 2013 20:33:59 +0200
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: ANNOUNCE: DJGPP port of GCC-4.8.2 (DJGPP v2.04 only)
References: <201310162005 DOT r9GK5npk027905 AT delorie DOT com>
In-Reply-To: <201310162005.r9GK5npk027905@delorie.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

On 10/16/2013 10:54 PM, Andris Pavenis wrote:
> This is announcement of DJGPP port of GCC-4.8.2

There are several problems with this port:

1) backtrace command in GDB does not work reliably even for DWARF2.
Seems that I have fixed that, but the fix is tested currently with
gcc-4.9-20131101 snapshot only. I used xgcc.exe from stage3 of
build (for example 'gdb --args xgcc.exe --help') present in
GDB build directory for testing (xgcc.exe gets installed as
gcc.exe by 'make install').

2) some executables in RPM packages were not stripped, so
unnecessarily bloating packages were generated

3) Old stuff: DWARF3 and DRAWF4 debugging information
causes problems. DJGPP is not the only target for which
DRAWF2 is the default. darwin also defaults to DRAWF2.
I do not know why that is so. The problems really could
really be in one of gcc and gdb.

I'll upload updated build after testing when I'll have it.

Andris