X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Date: Fri, 27 Jan 2012 08:48:32 +0200
From: Eli Zaretskii <eliz AT gnu DOT org>
Subject: Re: Abort when compiling using COFF debug format (-gcoff)
In-reply-to: <4faf5c37-ca50-4bd0-9081-3ada327099a5@h6g2000yqk.googlegroups.com>
X-012-Sender: halo1 AT inter DOT net DOT il
To: djgpp AT delorie DOT com
Message-id: <83sjj1zlmn.fsf@gnu.org>
References: <201201262112 DOT 52030 DOT juan DOT guerrero AT gmx DOT de> <83wr8eywzf DOT fsf AT gnu DOT org> <4faf5c37-ca50-4bd0-9081-3ada327099a5 AT h6g2000yqk DOT googlegroups DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: Rugxulo <rugxulo AT gmail DOT com>
> Date: Thu, 26 Jan 2012 15:01:08 -0800 (PST)
> 
> > Sounds like the COFF debug info generation has bit-rotted in GCC.
> > Nothing new here, no other platform uses COFF AFAIK.
> 
> What about ECOFF and XCOFF? (Tru64 ?? AIX ??) And I'd assume PE/COFF
> still uses most of the same COFF sources too. (Or did you only meant
> COFF debug info?

Yes, I only meant COFF debug info, and I even wrote that explicitly
(see above).

> Dunno, it has vaguely worse support for C++ by default, so perhaps
> that's why.) But yeah, GCC and BinUtils seem to focus mostly on ELF
> these days (see Gold linker).

Again, this is not about the object format, this is about debug info
format.  AFAIK, MinGW uses PE/COFF for the object format, but defaults
to DWARF for debug format.